Any tutorials on how to extract the stock kernel in case I want to reinstall it later? I'd like to test out other kernels but I don't see any source for stock EC05 kernel only. With just a kernel update.zip I wouldn't have to reodin the phone to go back to stock and lose all my data.
poit said:
Any tutorials on how to extract the stock kernel in case I want to reinstall it later? I'd like to test out other kernels but I don't see any source for stock EC05 kernel only. With just a kernel update.zip I wouldn't have to reodin the phone to go back to stock and lose all my data.
Click to expand...
Click to collapse
Open the zip for the Di18 to EC05 update with winrar or 7zip, copy and paste the zImage into one of the zips for another kernel.
mattallica76 said:
Open the zip for the Di18 to EC05 update with winrar or 7zip, copy and paste the zImage into one of the zips for another kernel.
Click to expand...
Click to collapse
Don't see a zImage file in there. I did a full search in the zip.
poit said:
Don't see a zImage file in there. I did a full search in the zip.
Click to expand...
Click to collapse
it might say boot.img.p
You would have to rename it zImage
mattallica76 said:
it might say boot.img.p
Click to expand...
Click to collapse
Found it.
So, just rename it zimage, open up ANY kernel zip file I have and replace the existing zimage file with this one?
Sounds too easy.
poit said:
Found it.
So, just rename it zimage, open up ANY kernel zip file I have and replace the existing zimage file with this one?
Sounds too easy.
Click to expand...
Click to collapse
I do it all the time, but make sure you name it zImage, not zimage.
poit said:
Any tutorials on how to extract the stock kernel in case I want to reinstall it later?
Click to expand...
Click to collapse
Sure, you can do it from a root shell (ConnectBot Local or "adb shell"):
Code:
su
cat /dev/block/bml7 > /sdcard/zImage
mattallica76 said:
it might say boot.img.p
Click to expand...
Click to collapse
That's not actually a kernel image, but a binary diff.
I'm not sure what happens if one restores it to the kernel partition directly. I imagine it's quite likely the phone won't boot though.
mkasick said:
Sure, you can do it from a root shell (ConnectBot Local or "adb shell"):
Code:
su
cat /dev/block/bml7 > /sdcard/zImage
That's not actually a kernel image, but a binary diff.
I'm not sure what happens if one restores it to the kernel partition directly. I imagine it's quite likely the phone won't boot though.
Click to expand...
Click to collapse
Ahh yes, thanks. Here is the update.zip for the stock kernel for whoever needs it. Credit for the update script goes to nubecoder.
mkasick said:
Sure, you can do it from a root shell (ConnectBot Local or "adb shell"):
Code:
su
cat /dev/block/bml7 > /sdcard/zImage
That's not actually a kernel image, but a binary diff.
I'm not sure what happens if one restores it to the kernel partition directly. I imagine it's quite likely the phone won't boot though.
Click to expand...
Click to collapse
Thanks, that may have saved me from an hour of headaches.
I ran those commands from terminal emulator and it seemed to work. Now as I understand it, I can just use the update.zip file for any kernel I have and insert this zImage I just created in place of the one in the file.
Thanks.
I tried cat /dev/block/bml7 > /sdcard/zImage. My zImage is 7.5MB
Is that right?
dangdang said:
I tried cat /dev/block/bml7 > /sdcard/zImage. My zImage is 7.5MB
Is that right?
Click to expand...
Click to collapse
Are you running stock EC05?
I attached an install zip of the stick EC05 kernel in post #8 of this thread. It's only 5.76 MB
Yeah stock EC05. I odin'd to DI18 then applied the update zip for EC05. Did you get your zImage from the cat command?
dangdang said:
I tried cat /dev/block/bml7 > /sdcard/zImage. My zImage is 7.5MB
Is that right?
Click to expand...
Click to collapse
Yes, well, almost.
/dev/block/bml7 is actually the kernel partition. The kernel itself doesn't actually take up the entire partition, so everything beyond 5 MBish is junk.
If you knew the exact size of the EC05 stock kernel, you could truncate "/sdcard/zImage" to that size and it would be identical to the kernel as shipped in an Odinable tar file.
For backup purposes, the extra "junk" doesn't really matter. You can still flash the 7.5 MB "zImage" with Odin, Heimdall, or redbend_ua (which update.zips use) all the same.
Ok that makes sense thanks. So 7.5MB is the largest kernel that can be compiled for our phones? Funny that sasmung left room for a bigger kernel but not a system partition.
dangdang said:
Yeah stock EC05. I odin'd to DI18 then applied the update zip for EC05. Did you get your zImage from the cat command?
Click to expand...
Click to collapse
No, I extracted it from the ACS untouched EC05 here-
http://forum.xda-developers.com/showthread.php?t=1003447
mattallica76 said:
No, I extracted it from the ACS untouched EC05 here-
http://forum.xda-developers.com/showthread.php?t=1003447
Click to expand...
Click to collapse
But....that rom didn't work. No data. Not sure I have confidence it that kernel.
poit said:
But....that rom didn't work. No data. Not sure I have confidence it that kernel.
Click to expand...
Click to collapse
I don't think the issue was the kernel. That build had an issue updating the profile which in turn caused data to not function. But even if it doesn't work, you just flash one that does. No big deal.
The kernel that is in the ota update zip is not a full kernel it is only a patch file.
skeeterslint said:
The kernel that is in the ota update zip is not a full kernel it is only a patch file.
Click to expand...
Click to collapse
understood. But the extract code mentioned earlier seems to extract the full kernel from the phone .
poit said:
understood. But the extract code mentioned earlier seems to extract the full kernel from the phone .
Click to expand...
Click to collapse
Yes that will pull the stock kernel.
Related
Like the title says, does damageless' sprintupdate2.zip have apps2sd enabled? I flashed it and all my apps appear to be installing on the device memory. What am I missing here? I wiped everything before flashing and partitioned my SD card.
I think sprintupdate2.zip was strictly the sprint update + root + busybox - some bloatware.
I wouldn't think he enabled apps2sd on it.
Kcarpenter said:
I think sprintupdate2.zip was strictly the sprint update + root + busybox - some bloatware.
I wouldn't think he enabled apps2sd on it.
Click to expand...
Click to collapse
Okay, follow up question: what's the best method for enabling apps2sd on Hero 2.1?
chapaj said:
Okay, follow up question: what's the best method for enabling apps2sd on Hero 2.1?
Click to expand...
Click to collapse
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Kcarpenter said:
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Click to expand...
Click to collapse
Bust open Damage 2.08.1 and grab his Boot.img and his a2sd script in /system/bin.....then put them in the ROM you are using.
Kcarpenter said:
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Click to expand...
Click to collapse
I've got the partitions ready to go. I just don't know how to pull the script. Does anyone have a guide on how to do this?
Konikub said:
Bust open Damage 2.08.1 and grab his Boot.img and his a2sd script in /system/bin.....then put them in the ROM you are using.
Click to expand...
Click to collapse
Okay, I've added those the sprintupdate2.zip that I'm using. I can then flash that over my existing ROM without wiping?
chapaj said:
Okay, I've added those the sprintupdate2.zip that I'm using. I can then flash that over my existing ROM without wiping?
Click to expand...
Click to collapse
Shouldn't hurt.
Kcarpenter said:
Shouldn't hurt.
Click to expand...
Click to collapse
That didn't work. I get:
E:Wrong digest:
boot.img
E:Verification failed
Installation aborted.
chapaj said:
That didn't work. I get:
E:Wrong digest:
boot.img
E:Verification failed
Installation aborted.
Click to expand...
Click to collapse
Did you resign the zip after you modified it?
use fresh kitchen or avabox
Kcarpenter said:
Did you resign the zip after you modified it?
use fresh kitchen or avabox
Click to expand...
Click to collapse
I had no idea i had to do that. I'm researching how to do that now. I don't suppose anyone could do it and throw up here as an attachment?
Post it up.
The first SprintUpdate that Damage released, I put the A2SD add-ons in it. If anyone wants me to do it again, let me know and I'll go do it.
EDIT: That was the SprintUpdate2 that I put the add-ons to. http://www.darktremor.info/files/2.1/sprintstock-21-a2sd-signed.zip
tkirton said:
The first SprintUpdate that Damage released, I put the A2SD add-ons in it. If anyone wants me to do it again, let me know and I'll go do it.
EDIT: That was the SprintUpdate2 that I put the add-ons to. http://www.darktremor.info/files/2.1/sprintstock-21-a2sd-signed.zip
Click to expand...
Click to collapse
I dl'd tkirktons darktremor and followed steps in his discussion thread posted above and worked perfectly. Thanks tkirkton!
Quick question. Can the New OC kernel be added to the damageless sprint leaked rom?
Anyone able to post a system dump of a GTablet that is stock with the latest OTA applied? I want to look at the stock framework and see about creating my own custom ROM - I am coming from the Android phone dev environment and would love to start putting together a custom ROM and/or themes
Thanks in advance.
jerdog said:
Anyone able to post a system dump of a GTablet that is stock with the latest OTA applied? I want to look at the stock framework and see about creating my own custom ROM - I am coming from the Android phone dev environment and would love to start putting together a custom ROM and/or themes
Thanks in advance.
Click to expand...
Click to collapse
Download here: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3389-user.zip
Unpack system.img with unyaffs, a binary exists for both windows and linux on the web.
Might have to run as admin in windows: unyaffs.exe system.img
Linux: chmod +x unyaffs
./unyaffs system.img
rothnic said:
Download here: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3389-user.zip
Unpack system.img with unyaffs, a binary exists for both windows and linux on the web.
Might have to run as admin in windows: unyaffs.exe system.img
Linux: chmod +x unyaffs
./unyaffs system.img
Click to expand...
Click to collapse
Thanks! It's what I needed. wasn't sure if that update was one that completely started over or just patched what existed.
Their updates are complete system.img wipes, so 3389 is a good starting point.
roebeet said:
Their updates are complete system.img wipes, so 3389 is a good starting point.
Click to expand...
Click to collapse
In the Android phone arena, we see more update.zip's that are applied via a custom recovery (CW or AmonRA) since we haven't fully cracked (most) system recoveries. Here it looks like any update.zip can be used with the system recovery...
We also don't flash system images, instead we format the SYSTEM partition and then copy the new system or data package over via:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
What are the parameters for creating an update.zip for this? What signed process is needed with the system recovery?
What custom roms are you familar with? I really like Apex on my droid x
jerdog said:
In the Android phone arena, we see more update.zip's that are applied via a custom recovery (CW or AmonRA) since we haven't fully cracked (most) system recoveries. Here it looks like any update.zip can be used with the system recovery...
We also don't flash system images, instead we format the SYSTEM partition and then copy the new system or data package over via:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
What are the parameters for creating an update.zip for this? What signed process is needed with the system recovery?
Click to expand...
Click to collapse
Unsure what you are saying exactly. Since they don't have to be signed, I hardly ever mess with it. Most of mine have been canabalized stock update.zip's, like you downloaded.
Also, typically we have had better luck with updater-script(updater-binary required and found in your downloaded 3389 update) format/syntax compared to the update-script one.
lilgotti56 said:
What custom roms are you familar with? I really like Apex on my droid x
Click to expand...
Click to collapse
On the Evo, there's (to name a few):
- Myn's
- Azrael X
- Calkulin's EViO
All have taken the stock, and removed as much bloat as is possible and then added in enhancements that make use of the full capabilities of the phone, etc.
rothnic said:
Unsure what you are saying exactly. Since they don't have to be signed, I hardly ever mess with it. Most of mine have been canabalized stock update.zip's, like you downloaded.
Also, typically we have had better luck with updater-script(updater-binary required and found in your downloaded 3389 update) format/syntax compared to the update-script one.
Click to expand...
Click to collapse
That is great they don't need to be signed - much easier to put together.
What has been the issue with the update-script process?
Click HERE
Working on trying to get some deodex love going...
Just got Xoom WiFi tonight, let me know what I can do to help out the xoom wifi community.
I am curious. How were you able to extract the stock system dump image for the wifi version? Could you put down instructions since I am trying to learn these things.
Just a quick heads up. Moto was handing out DMCA notices on sysdumps. You may wanna save it for those who make it to #xoom on freenode.
bigrushdog said:
Just a quick heads up. Moto was handing out DMCA notices on sysdumps. You may wanna save it for those who make it to #xoom on freenode.
Click to expand...
Click to collapse
Moto can suck an egg...will post link on my site :-D
Feel free to post the link on irc...
teamdefuse.com
Angdroid said:
Click HERE
Working on trying to get some deodex love going...
Just got Xoom WiFi tonight, let me know what I can do to help out the xoom wifi community.
Click to expand...
Click to collapse
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
ericdabbs said:
I am curious. How were you able to extract the stock system dump image for the wifi version? Could you put down instructions since I am trying to learn these things.
Click to expand...
Click to collapse
Install latest moto drivers
Install Android SDK
Enable USB Debug in Xoom settings
Open command prompt
Create new directory
CD to new directory
At command prompt type: adb pull /
files will be dumped to current path of command prompt
I Got the one (well, couple a clicks) root and unroot covered. You can check that one off the list. Thread open over yonder if you want to give it a spin... I am just uploading the newest version that one click updates to HRI66.
jwtyler said:
I Got the one (well, couple a clicks) root and unroot covered. You can check that one off the list. Thread open over yonder if you want to give it a spin... I am just uploading the newest version that one click updates to HRI66.
Click to expand...
Click to collapse
good, will be looking for it. NOW, an easy way to overclock to 1.5 would be wonderfull...
ericizzy1 said:
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
Click to expand...
Click to collapse
1 is being worked on...NVM...Check out jwtyler one click root thread.
2 & 4 Going to try the same method that was used for Droid2 and DroidX. Create module for OC. I have not had time yet to look at kernel but I see someone is already creating kernels so should be able to do it from kernel with multiple settings; not sure if kernel behaves same way as it does in Droid.
3 Not sure if bootstrap (clockwork recovery) is available yet for Xoom WiFi but if it is just make a backup before you mod anything.
Not sure what you are talking about with 5 and 6 ... I am a Xoom noob, only been out of box for a couple of hours
ericizzy1 said:
good, will be looking for it. NOW, an easy way to overclock to 1.5 would be wonderfull...
Click to expand...
Click to collapse
Sweet
Drop me a line if you want to try to bang out some stuff together...
Thanks Angdroid for the system dump. I downloaded a copy of the system dump for kicks. I will keep it on my hard drive in case anyone loses it and needs a backup copy.
Hopefully we can create a stock boot.img soon for us wifi owners in case something goes wrong or need to return it to factory state. It looks like from the system dump we have access to the stock bcm4329.ko wifi driver.
ericdabbs said:
Thanks Angdroid for the system dump. I downloaded a copy of the system dump for kicks. I will keep it on my hard drive in case anyone loses it and needs a backup copy.
Hopefully we can create a stock boot.img soon for us wifi owners in case something goes wrong or need to return it to factory state. It looks like from the system dump we have access to the stock bcm4329.ko wifi driver.
Click to expand...
Click to collapse
Any word on the stock boot.img?
fabian29906 said:
Any word on the stock boot.img?
Click to expand...
Click to collapse
I am not a developer. I just meant a community as a whole come up with the files for the stock boot.img.
Still no word from Motorola of providing the stock boot.img for the wifi Xoom.
Do you think it's possible to extract languages in Wifi firmware to flash 3g xoom?
Or flash with entire wifi firmware?
I don't think the adb pull way is the best way at it.
Creating an actual image using dd will retain symlinks and mod perms (not owners).. but it also won't dump a bunch of tiny >1kb files on your computer (whose cluster size may be over 4kb).. plus you can mount it as a loop device..
adb shell
# busybox dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/sdcard/system.img
and then if you want
adb pull /mnt/sdcard/system.img
but I wouldn't.. just using the mtp interface is faster..
sausalito said:
Do you think it's possible to extract languages in Wifi firmware to flash 3g xoom?
Or flash with entire wifi firmware?
Click to expand...
Click to collapse
What do you mean? are you talking about the ./system/vendor/firmware/fw_bcm4329.bin
I just compared the two system images for both devices
fw_bcm4329_mfg.bin is the only file with a matching checksum..
I gotta run.. otherwise i'd check the version with a hex editor..
I doubt you're talking about the wifi firmware anyways..
ericizzy1 said:
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
Click to expand...
Click to collapse
Ya! A color calibration app would be awesome!
Azrael X 4.0
100mbit:
http://gititbit.ch/xRx3 - Xoom_Wifi_3.0.1.zip
That's what I did for this image. http://www.mediafire.com/file/2fknnmy6nw6i19n/StockWiFiSystem.zip
Note, you need to be able to mount a YAFS2 filesystem to read the contents.
Blades said:
I don't think the adb pull way is the best way at it.
Creating an actual image using dd will retain symlinks and mod perms (not owners).. but it also won't dump a bunch of tiny >1kb files on your computer (whose cluster size may be over 4kb).. plus you can mount it as a loop device..
adb shell
# busybox dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/sdcard/system.img
and then if you want
adb pull /mnt/sdcard/system.img
but I wouldn't.. just using the mtp interface is faster..
Click to expand...
Click to collapse
Sent from my Xoom using Tapatalk
can someone post the 3.1 wifi-model USA system
(i need build.prop)
can anyone send me the names of the init.devicename.rc and the unvented.device.rc? they are located in the kernel ramdisk
alex1301 said:
can anyone send me the names of the init.devicename.rc and the unvented.device.rc? they are located in the kernel ramdisk
Click to expand...
Click to collapse
Hi, here are the contents of the folder:
http://i.imgur.com/bxbK3.png
And attached is latest boot.img (kernel 3.0.8 from dzo's Aurora ICS) and the decompressed files if you need that...
i am quite ready with the rom. only thing is i have this problem.
[email protected]:~/Desktop/BootScripts$ sudo perl repack-bootimg.pl /home/ubuntu/Desktop/BootScripts /home/ubuntu/ramdisk /home/ubuntu/Desktop
1891 blocks
sh: mkbootimg: not found
repacked boot image written at /home/ubuntu/ramdisk-repack.img
but there is no file when i repack the kernel
alex1301 said:
i am quite ready with the rom. only thing is i have this problem.
[email protected]:~/Desktop/BootScripts$ sudo perl repack-bootimg.pl /home/ubuntu/Desktop/BootScripts /home/ubuntu/ramdisk /home/ubuntu/Desktop
1891 blocks
sh: mkbootimg: not found
repacked boot image written at /home/ubuntu/ramdisk-repack.img
but there is no file when i repack the kernel
Click to expand...
Click to collapse
Can you post the un packed files? I could try to repack them
I think I know what the problem is, you need to have mkbootimg... Here it is, put it in /bin and then rerun the repack script
EDIT: for some reason, attachments are always corrupt... but here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=475249&d=1293574570
http://www.mediafire.com/?y5ur5lc4q7d5148
http://www.mediafire.com/?vl44nay131u8ofz
sent them please repacked back
alex1301 said:
http://www.mediafire.com/?y5ur5lc4q7d5148
http://www.mediafire.com/?vl44nay131u8ofz
sent them please repacked back
Click to expand...
Click to collapse
Here it is.
But your error was because you probably didn't have mkbootimg on your system
are you ready?
alex1301 said:
are you ready?
Click to expand...
Click to collapse
I've posted the boot.img right now
I hope there's nothing wrong with it... to repacked the files, I put all the files from your both zip files in one folder, then run repack-bootimg.pl script over boot.img-kernel as argument, is this correct?
yes man thanks. i will give you credits in the rom section.
do you know if i can use the updater script form aurora?
alex1301 said:
do you know if i can use the updater script form aurora?
Click to expand...
Click to collapse
I guess yes, the script, if I'm not wrong, only formats partitions and copies the ROM files to the appropriate locations and sets permissions... try using it, or post the ROM here and I'm sure someone can work it out if it doesn't work...
Cheers
Sent from my U8800
i will release it in a couple of minutes. so when the script is not working, someone other can fix it
have i also to replace the updater-binary?
I don't think that's needed, the binary I assume is the same for different ROMs, only the script changes... but I would to be sure good luck!
Sent from my U8800
i can't sign this bull**** apk
alex1301 said:
i can't sign this bull**** apk
Click to expand...
Click to collapse
What do you mean? I was hoping for a release today :-( good luck man...
Tomorrow I'll try posting from desire z... can you post a link for a guide? Thank you...
Sent from my U8800
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: )