Related
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 there, I've just discovered the insane amount of memory used by the system (like 2GB+). I've just discovered that the CM11 just uses 500+MB. And here popped the question: how can i shrink the partition and give the unused space to the sdcard0 partition? Is it possible to do it whitout loosing data?
I got S4 with the Snapdragon, CM11 Installer (i can always flash the snapshot if needed).
Then googling around i found few things not exactly easy to use (unfortunately I'm not a developer); while reading those things it popped in my mind "what if i flash another .zip from recovery? Will it broken the phone? What if I'll flash stock from Odin?"
So here am I, asking on to you guys Thank you for the patience
On the i9500 flashing the chinese pit file reduces the system size.
But again flashing pit files in itself is a big deal. It can lead to a hardbrick.
So basically its better to stay happy with what Samsung has given us
Sent from my GT-I9500 using XDA Free mobile app
DeepankarS said:
On the i9500 flashing the chinese pit file reduces the system size.
But again flashing pit files in itself is a big deal. It can lead to a hardbrick.
So basically its better to stay happy with what Samsung has given us
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
Probably you're right but i want to dare
Lamba92 said:
Probably you're right but i want to dare
Click to expand...
Click to collapse
Haha unfortunately the chinese pit is for i9500.
Find a similar one for the i9505. I bet there would be none, or if there are @Lennyz1988 can help you
"If someone helps, never forget to hit thanks ? "
Weeks ago I wrote this in another thread:
I'm who discovered the way to repartition three STE devices (S Advance, Ace II and S3 Mini).
After any kind of test on my I9505 I can sadly say that it's IMPOSSIBLE to repartition.
-PIT files are signed, if we don't have that signature to sign the file we can't use custom PITs.
-Size of the partitions are specified by three text entries (six in HEX) in some offsets before partition's name.
-Signature is 48 blocks long (768 offsets) and it's at the very end of the untouched file. Modifying PIT through PIT Magic totally breaks signature (is no longer inside file) and simply copy-paste works only when you don't modify things of file. It's generated depending on file lenght in blocks, any character inside and partitions' size and names, modifying also a single value of an offset means that we require a new signature because previous one is no longer valid.
-Device has a PIT partition, flash filename is MSM8960.pit. Isn't showed in dev/block since it's protected and hidden, creating a Odin-flashable package and trying to flash doesn't work since flash ends fine but new PIT isn't sent to device.
-When you tick Repartition in Odin and choose a PIT file, rightly after you start to flash that file is compared to the one inside PIT partition, if aren't 1:1 Odin refuses to flash and Download Mode screen gives "Secure Check Fail: PIT"
-KNOX bootloaders (4.3-4.4) have eMMC write protection for partition table, there's also a GPT backup inside. If you try to repartition mmcblk0 using parted or fdisk in ADB, commands end fine but nothing changes. After this operation, partitions are no longer accessible by recovery but just restart your device and let the magic happen (partitions agian accessible, nothing changed).
-Theoretically repartition through parted is possible with a non-KNOX bootloader (4.2) since seems that doesn't have eMMC write protection for partition table and GPT backup. I can't confirm because I have last bootloader.
Click to expand...
Click to collapse
Inviato dal mio GT-I9505
@AntaresOne You're back eh? hopefully and finally. ?
"If someone helps, never forget to hit thanks ? "
DeepankarS said:
@AntaresOne You're back eh? hopefully and finally. ?
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Not fully back but yes, lol
Inviato dal mio GT-I9505
Hello!
I've been trying to see if there's any root exploits, ROMs, whatever for this phone. Is it Hamachi (4012) compatible? Or is it another species? It does seem there's not much about it.
The only thing I've found is this mail thread.
comments DOT gmane DOT org / gmane DOT comp DOT mozilla DOT devel DOT b2g / 12487
The Fire C is a Jelly Bean based one. Start from there.
If I can successfully flash mine will post results. Wish me luck.
resetreboot said:
Hello!
I've been trying to see if there's any root exploits, ROMs, whatever for this phone. Is it Hamachi (4012) compatible? Or is it another species? It does seem there's not much about it.
Click to expand...
Click to collapse
mancvso said:
The only thing I've found is this mail thread.
comments DOT gmane DOT org / gmane DOT comp DOT mozilla DOT devel DOT b2g / 12487
The Fire C is a Jelly Bean based one. Start from there.
If I can successfully flash mine will post results. Wish me luck.
Click to expand...
Click to collapse
Nope. Bricked phone.
Anyone knows how to use this files?
forum DOT gsmhosting DOT com / vbb / f272 / flash-file-request-alcatel-4019x-1883599
Where did you find these files? Can you point me to them?
Maybe I can make something out of it. The MTK Droid Tools is totally unable of dumping anything from this phone and it's supposedly designed for these kind of phones (the chipset is a MediaTek).
If only I could snatch the boot image...! But the /dev/ block devices do not make any sense to me, otherwise I'd have at least something to go back when I screw the boot loader.
The URL is in the post above, just replace " DOT " with "." and delete spaces.
Anyway, the direct link is
mediafireDOTcom/?t6x77dxpb9bucbf
Which one is boot, system, userdata? Do you have the original file sizes?
I've tried with various Hamachi (4012X) boot.img but none of them works.
PD: I cannot post links.
I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.
Wonderful! This is really useful info.
Now we can try to couple it with the FFOS SDK and try to get root and maybe upgrade to 2.0...
D'loading so I can start hacking...
resetreboot said:
Wonderful! This is really useful info.
Now we can try to couple it with the FFOS SDK and try to get root and maybe upgrade to 2.0...
D'loading so I can start hacking...
Click to expand...
Click to collapse
Please do so! An upgrade to 2.x is crucial even for copy/pasting text.
mancvso said:
I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.
Click to expand...
Click to collapse
Great news, remember you can type *#3228# to know what are all these filenames in your device.
I have a 4019M (sold unlocked in this country) and I am interested on this, however I don't have experience flashing yet, as this is my first smartphone. If you need to do some tests from here for this particular device to get root and upgrades, feel free to ask!
This device is qualcomm based and gonk is jelly bean based, if I recall correctly.
Some news, they finally uploaded this month 4019X / 4019A GPL compliance sources into sourceforge · net / projects / alcatel / files /
Some progress to get a proper factory image
When using One Touch Update, I tried to figure what happens with the factory image download from the vendor. It downloads a bunch of 64 KiB files stored in a downloaded/ subdir of the programfiles application folder. They are downloaded via TCP, not using HTTP. Once the download is complete, out1.data and out2.data are generated, I guess all these files get somewhat assembled into these. They are placed in the programfiles application folder too, 203 MiB each. They look like a couple of Android sparse image files, according to header magic numbers. These files should be copypasted somewhere before ending the flash operation and closing the application, otherwise they will be deleted. Maybe these files contain interesting stuff :good:. There is also a log file showing addresses where is flashing and sizes of the images of the factory flashing operation.
Maybe some USB sniffing is worth, but not tested.
4019X Brick
Hi guys.
I have a 4019X bricked becasuse i tried to install a wrong system.img.
Can you upload again the factory flash images? The mediafire link is broken.
I made a backup of the original system with adb pull /system /system as mozilla´s recommend in the Firefox OS build prerequisites.
But i dont know how to compile to restore my phone. I tried this:
ANDROIDFS_DIR=<path to system backup> ./config.sh tarako
ANDROIDFS_DIR=<path to system backup> ./build.sh
but always fail.
If you dont know, can you tell me how to use the source code of alcatel to unbrik my phone:
sourceforge.net ... OT_FF_4019X_20150408.tar.xz
Thanks
Backup of the stock One Touch Fire C files
https://www.dropbox.com/s/nzn6g4qhh585ho4/4019X-2[X=A,B,C,D]TBHU1.rar?dl=0
Please keep us informed on any progress, now that Firefox has freed itself.
can u tell me if this rom has portuguese language? i need 4019x android or firefox with portuguese language? or anyway to add language?
best regards
mancvso said:
I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.
Click to expand...
Click to collapse
Hi! I can not fix my Alcatel OT- 4019A yet. ¿could you please help me with that?
I don't know exactly what do with that archives.
Thanks!
Gsmfanatic said:
can u tell me if this rom has portuguese language? i need 4019x android or firefox with portuguese language? or anyway to add language?
best regards
Click to expand...
Click to collapse
The firmware doesn't have the Portuguese language, flashed it myself ...
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: )
Hey, I noticed while looking through the Stock Firmware AP file, that in meta-data/fota.zip there are .jar files that have to do with package signing. Only issue is that the zip is password protected. If someone has the Compute power and skills to decrypt a zip and look at the jar files and ****, maybe we could find a way to sign our own TWRP recoveries and roms. Just a thought, i'll post a link to the fota.zip file i was talking about in a bit if anyone wants to take a crack at it. (Google drive is taking forever to upload cause of AT&T's ****ty DSL speeds, sorry)
Download Link: htt*ps:/*/drive.*google*.com/file/*d/0B9tb-svjqaVD*b3Y0V0tXR3drSzA/vie*w?usp=sharing (Remove all *'s from link, stupid 10 post until you can post links limitation)
Thanks,
Lavavex
Did you saw this Thread?
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
About fota.zip...
Did you heard about plain text attack?
In few Seconds... minutes done... no password required but you can unpack.
Best Regards
Yesterday I have download this fota.zip... and yes... same password as for instance from my prior test with:
SM-J330F and 1 more...
Here are the 3 keys to decrypt if somebody want try...
Code:
2b4d493c
6142b289
1b7024aa
Code:
Key0
Key1
Key2
I have used Advanced Archive Password Recovery from elcomsoft...
Best Regards
adfree said:
Yesterday I have download this fota.zip... and yes... same password as for instance from my prior test with:
SM-J330F and 1 more...
Here are the 3 keys to decrypt if somebody want try...
Code:
2b4d493c
6142b289
1b7024aa
Code:
Key0
Key1
Key2
I have used Advanced Archive Password Recovery from elcomsoft...
Best Regards
Click to expand...
Click to collapse
Which will allow unpacking of the above zip? I thought it needed a zip password.
osm0sis said:
Which will allow unpacking of the above zip? I thought it needed a zip password.
Click to expand...
Click to collapse
We never found the Password... but for Decryption you need only these 3 Keys...
They can be easily found in few Minutes... with the right Tool...
Code:
2b4d493c
6142b289
1b7024aa
Here Key0 Key1 Key2 for Samsungs fota.zip...
This is really no rocket science...
Simple read about plain-text attack...
You can see all filenames...
You can see all filesizes etc...
Many files are floating around the Internet... to create ZIP for attack...
Then result is in few Minutes possible... :angel:
Use these 3 Keys in Tool:
Code:
Advanced Archive Password Recovery
And try self to unpack...
Best Regards
Edit 1.
Screenshot added...
Then maybe more clear...
Trial Version have mabye limtations... but to see it work... it is enough to play with trial.
@adfree or to anyone who can answer.
Quick question, what are the legal limitations to what is going on here? I may or not have a file from inside the fota.zip, but will sharing it put me in the legal wrong? If it is within the legal boundaries, I'd be happy to upload it for anyone to take a look at, but I don't want to land on the wrong side of the law by doing so. Please do let me know, as this is the most exciting development we've had when it comes to bootloader unlocking in a while. Also, it seems as though we can't view the entirety of the contents of the fota.zip with the trial version of the zip extraction tool mentioned in this thread, so if someone with more knowledge about this can confirm we could unlock our bootloaders with the contents of the zip (based on what is currently known about this), I'd be happy to bite the bullet of paying for the premium version given we can do this within the boundaries of the law.
Thanks.
1.
Maybe you can answer your question self...
Samsung PROTECTED this ZIP with password.
2.
IMHO it is Kernel related...
Yeah I know... Boot is every irritating...
But it is not sboot.bin related...
3.
About decrypting all files...
There are floating around Command Line Tool...
Code:
pkcrack
Try to Google it...
I have not tried...
I am 1 click Button user...
Best Regards
zipdecrypt from the pkcrack package plus those 3 keys worked flawlessly. :good:
Edit: Crazy number of utilities in this zip, but no script to run them all, and a lot of references to external files. No smoking gun like a "sbootimg_signer" binary or anything to make their proprietary footer signature, and no Samsung signature files.
the password for that zip is fotatest1234
Correct. All fota zips passwords are fotatest1234
Drdra3 said:
Correct. All fota zips passwords are fotatest1234
Click to expand...
Click to collapse
@lavavex , @osm0sis
Yes it is, but now the question still to be answered is, do the tools within the fota.zip file, actually work for legitimately repacking the boot/recovery image? Because in the fota.zip I checked from Android Pie's release it mentioned the "user/test-keys" and very much so had all of the compiled tools to actually patch a system and create and ADB flashable zip for stock recovery.
Could we technically make a signed sideloadable update.zip if the the update package was created on the device itself? The scripts included, along with the updated compiled binary tools, really do seem to be the Toolkit we've been looking for but have overlooked. I haven't tested it out fully, but I'm still reading about how to proceed. It isn't just the S7 either. So are the tools customized to the device, the android branch, or the bootloader?
Delgoth said:
@lavavex , @osm0sis
Yes it is, but now the question still to be answered is, do the tools within the fota.zip file, actually work for legitimately repacking the boot/recovery image? Because in the fota.zip I checked from Android Pie's release it mentioned the "user/test-keys" and very much so had all of the compiled tools to actually patch a system and create and ADB flashable zip for stock recovery.
Could we technically make a signed sideloadable update.zip if the the update package was created on the device itself? The scripts included, along with the updated compiled binary tools, really do seem to be the Toolkit we've been looking for but have overlooked. I haven't tested it out fully, but I'm still reading about how to proceed. It isn't just the S7 either. So are the tools customized to the device, the android branch, or the bootloader?
Click to expand...
Click to collapse
Presumably what I previously said still stands:
osm0sis said:
Crazy number of utilities in this zip, but no script to run them all, and a lot of references to external files. No smoking gun like a "sbootimg_signer" binary or anything to make their proprietary footer signature, and no Samsung signature files.
Click to expand...
Click to collapse