Related
Hi all! I'm not a dev but i really want to do something for this phone so i'm trying to build a custom kernel.... if anyone have tried the same report here the issue, i will do the same!
I have the pre-requisites for compiling a kernel set up. However I am more interested in getting ClockworkMod Recovery working on our phone as that will encourage developers and we can then start looking at getting CyanogenMod 7. I made a topic here asking for help but I haven't received any replies yet.
I have just compiled a kernel but it doesn't work.... this because - i think - i used the initramfs provided by leshak for the i9000.... now i'm trying to extract from phone......
Kernel
Hi Skin1980, I also compiled a (stock) Kernel two weeks ago - problem is, Samsung does not use the "normal" way of storing it in a boot.img file. That is why I wasn't able to push it to the phone or at least fastboot it. I would be glad to hear from you how exactly this is possible, if you find out.
XDA_Bam said:
Hi Skin1980, I also compiled a (stock) Kernel two weeks ago - problem is, Samsung does not use the "normal" way of storing it in a boot.img file. That is why I wasn't able to push it to the phone or at least fastboot it. I would be glad to hear from you how exactly this is possible, if you find out.
Click to expand...
Click to collapse
I used the redbend_ua you can find here to write zImage to bml7.... how do you do with initramfs that is missed when you build the kernel?
Skin1980 said:
I used the redbend_ua you can find here to write zImage to bml7.... how do you do with initramfs that is missed when you build the kernel?
Click to expand...
Click to collapse
Have you managed to extract initramfs with redbend_ua?
If you don't mind, please take a look at this post. There is a step build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img. Because Samsung doesn't use this boot.img building a recovery looks tricky. Any suggestions would help.
rb210 said:
Have you managed to extract initramfs with redbend_ua?
If you don't mind, please take a look at this post. There is a step build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img. Because Samsung doesn't use this boot.img building a recovery looks tricky. Any suggestions would help.
Click to expand...
Click to collapse
I dumped the bml7 partition, i see that inside there's a zimage... but i'm not able to extract this f u c .......initramfs!!!!!
rb210 said:
Have you managed to extract initramfs with redbend_ua?
If you don't mind, please take a look at this post. There is a step build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img. Because Samsung doesn't use this boot.img building a recovery looks tricky. Any suggestions would help.
Click to expand...
Click to collapse
and if we can find the initramfs i think that is not difficult to modify the recovery to allow unsigned zip files installation
Perhaps, we could use parts of the following method:
h**p://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
To extract the ramdisk from the boot.img, they do the following:
Then, look for a bunch of zeroes followed by the hex 1F 8B (which is the magic number of a gzip file). Copy everything from the first line of the file, through the zeroes, and stopping at the 1F 8B. That is the kernel. Everything from the 1F 8B through the end is the ramdisk. You could save each of these files separately. In order to see the contents of the ramdisk, you need to un-gzip it and then un-cpio it.
Click to expand...
Click to collapse
I know that we don't have a boot.img, but we do have an image including kernel and ramdisk - this should be very similar. And if you can locate the named headers in the file, the extraction should work. Further info and some useful commands can be found behind the link.
Sadly, I won't have time to try this before next weekend...
XDA_Bam said:
Perhaps, we could use parts of the following method:
h**p://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
To extract the ramdisk from the boot.img, they do the following:
I know that we don't have a boot.img, but we do have an image including kernel and ramdisk - this should be very similar. And if you can locate the named headers in the file, the extraction should work. Further info and some useful commands can be found behind the link.
Sadly, I won't have time to try this before next weekend...
Click to expand...
Click to collapse
Which file are you referring to? I have some time, I can give it a shot.
EDIT: I found "initramfs.c" and its object file "initramfs.o" under GT-I9003_Kernel/kernel/Kernel/init from the Samsung opensource tarball. Don't think that helps us though.
@rb210: I mean the dumped bml7 partition. It's an image of a partition with a kernel and ramdisk in it, or did I misunderstand something?
PS: You could try "SGS kernel flasher" from the market. It's got a backup option - look if it does produce the same image of the bml7 partition (I tried it, it did a backup image of around 8MB on my SGSL, which is about the size of bml7, as far as I remember). It would be faster and easier to carry out than using a script.
XDA_Bam said:
@rb210: I mean the dumped bml7 partition. It's an image of a partition with a kernel and ramdisk in it, or did I misunderstand something?
PS: You could try "SGS kernel flasher" from the market. It's got a backup option - look if it does produce the same image of the bml7 partition (I tried it, it did a backup image of around 8MB on my SGSL, which is about the size of bml7, as far as I remember). It would be faster and easier to carry out than using a script.
Click to expand...
Click to collapse
But ramdisk=initramfs?
XDA_Bam said:
@rb210: I mean the dumped bml7 partition. It's an image of a partition with a kernel and ramdisk in it, or did I misunderstand something?
PS: You could try "SGS kernel flasher" from the market. It's got a backup option - look if it does produce the same image of the bml7 partition (I tried it, it did a backup image of around 8MB on my SGSL, which is about the size of bml7, as far as I remember). It would be faster and easier to carry out than using a script.
Click to expand...
Click to collapse
Ah I see what you mean. I was trying to figure out how to extract the initramfs from the opensource package from the Samsung website. I figure if they're providing the kernel and platform, there's got to be an initramfs somewhere. You'll are talking about trying to extract it from inside the phone itself.
I'm still not sure how this is going to fit in with porting Clockworkmod as per that method in the blog post because it's still an initramfs and not a boot.img. Getting custom recovery is vital to attracting development for this phone, we should not make the mistake of overlooking this.
Tools for extract initramfs from a zImage : https://github.com/project-voodoo/kernel_repack_utils
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?
Hello Guys,
I packed the rom in a flashable zip, it's pre-rooted and nut's dual recovery is included, also the kernel is included so need to flash that afterwards
Thanks to @zxz0O0 for his PRFCreator, @[NUT] for his dualrecovery, @Chainfire for root package, and me for combining their great work work for you
I got some reactions that root isn't working properly, So i will be working on a new version, but that will have to wait until i got Linux working and setup again (ages ago since i worked with Linux ) and made the new version. After that i might even consider tweaking it etc, but don't hold your hopes up yet, i don't have much spare time to work on it
SGP511
https://mega.co.nz/#!ndFxUCTR!xVE235NjuIFiugEofrQaWjWP5cLfSBffgyx1sIgV1ak
SGP512
https://mega.co.nz/#!bJ8lTJiA!vg4B_TSlKnwJPxm3WK5Rgc13h0ejx3Jq6x7LGtTu-6w
SGP521
https://mega.co.nz/#!TB9lULCI!v2m-wL4JGEDs_fIQt83Qrbmn0JerkMfL-aSIOh-mtVY
You should know that Playstation PS4 remote play Won't work due to Root.
If you want to use that wait for a different root/altered ps remote play app and just enjoy stock unrooted untill then
instructions:
make sure you are on a rom with recovery
flash this rom, wipe cache/dalvik cache, reboot
enjoy
Thanksss
R/W
Root Explorer does not switch /system in mode R/W
This work with SGP561?
Sent from my SGP561 using XDA Premium HD app
I don't think so. I'll see if i can make one for 561 tomorrow
Sent from my SGP521 using XDA Premium HD app
Bird40 said:
Root Explorer does not switch /system in mode R/W
Click to expand...
Click to collapse
I'm sorry to hear that. Haven't really tested it since i want to use ps4 remote play.
I'll see if i can make a new version later tomorrow
Sent from my SGP521 using XDA Premium HD app
crazymister said:
I'm sorry to hear that. Haven't really tested it since i want to use ps4 remote play.
I'll see if i can make a new version later tomorrow
Sent from my SGP521 using XDA Premium HD app
Click to expand...
Click to collapse
Did you modify the kernel "ramdisk" to make it insecure?
Generally with most ramdisks, you'll need to split the boot.img, unpack the ramdisk gz, and edit the line in the default.prop (might be in a different location)
Change this line from ro.secure=1 to ro.secure=0
Then repack ramdisk, and repack the boot.img
Virtuous Ten Studio should do this automatically when you split the boot.img.
Moscow Desire said:
Did you modify the kernel "ramdisk" to make it insecure?
Generally with most ramdisks, you'll need to split the boot.img, unpack the ramdisk gz, and edit the line in the default.prop (might be in a different location)
Change this line from ro.secure=1 to ro.secure=0
Then repack ramdisk, and repack the boot.img
Virtuous Ten Studio should do this automatically when you split the boot.img.
Click to expand...
Click to collapse
No i didn't do anything to the kernel. It's completely stock
Sent from my SGP521 using XDA Premium HD app
crazymister said:
No i didn't do anything to the kernel. It's completely stock
Sent from my SGP521 using XDA Premium HD app
Click to expand...
Click to collapse
There's the issue, and why you can't get /system RW.
On most devices, if you can get OEM Bootloader Unlock, then it's just a matter of modifying Ramdisk as stated above, then fastboot (flash) the new boot image. You can do a simple adb push and permissions for SU and SuperSU.apk.
When you split a boot.img, you get 2 parts basically, zimage (kernel) and ramdisk. Ramdisk you can edit.
As with the easyroot program (worked prior to .167), it used an exploit to split the bootimg, and modify ramdisk with the above parameters internally, then packing it back. Hence why it was copying it to a temp folder to do it's work. This was all great as we didn't need to unlock bootloader. But it doesn't negate the fact the ramdisk was still modified.
Get Virtuous Ten Studio here at XDA. Unpack the boot.img, make the change, pack it back and flash it. Should work. Program is pretty simple.
I just can't get it working right under Win 10, and not sure when I can get to it.
Moscow Desire said:
There's the issue, and why you can't get /system RW.
On most devices, if you can get OEM Bootloader Unlock, then it's just a matter of modifying Ramdisk as stated above, then fastboot (flash) the new boot image. You can do a simple adb push and permissions for SU and SuperSU.apk.
When you split a boot.img, you get 2 parts basically, zimage (kernel) and ramdisk. Ramdisk you can edit.
As with the easyroot program (worked prior to .167), it used an exploit to split the bootimg, and modify ramdisk with the above parameters internally, then packing it back. Hence why it was copying it to a temp folder to do it's work. This was all great as we didn't need to unlock bootloader. But it doesn't negate the fact the ramdisk was still modified.
Get Virtuous Ten Studio here at XDA. Unpack the boot.img, make the change, pack it back and flash it. Should work. Program is pretty simple.
I just can't get it working right under Win 10, and not sure when I can get to it.
Click to expand...
Click to collapse
That will be a problem for me since my bootloader is still locked. So i will not be able to flash an insecure kernel.
And im not going to unlock it anytime soon either, so if you want an insecure kernel you will have to build it yourself. In whatever environment. You can always start a VM with win/linux just to build it
And sorry if i sound harsh that'snot my intention. :good:
crazymister said:
That will be a problem for me since my bootloader is still locked. So i will not be able to flash an insecure kernel.
And im not going to unlock it anytime soon either, so if you want an insecure kernel you will have to build it yourself. In whatever environment. You can always start a VM with win/linux just to build it
And sorry if i sound harsh that'snot my intention. :good:
Click to expand...
Click to collapse
Naw, no offense taken. :highfive:
I hate unlocking mine as well, but eventually will probably have to. Just hate going through Sony to do it, as they will have my tab ID on record
Btw, i didn't use an easyroot utility but injected the root directly into the ROM. (not a nandroid backup, but downloaded the sony files, decrypted them, turned that into ftf and used the ftf to build a zip with root build into it
On the brief test i did, i did have root privileges, but i didn't do an extensive test because i only tested if root was there (used root checker), because i use the ps4 remote app :good: that just gives an error as soon as you have a superuser app installed
So from the reactions i got (and I'll change the op until i got a new, good working version) root isn't working properly, but working nonetheless
Sent from my SGP521 using XDA Premium HD app
crazymister said:
Btw, i didn't use an easyroot utility but injected the root directly into the ROM. (not a nandroid backup, but downloaded the sony files, decrypted them, turned that into ftf and used the ftf to build a zip with root build into it
On the brief test i did, i did have root privileges, but i didn't do an extensive test because i only tested if root was there (used root checker), because i use the ps4 remote app :good: that just gives an error as soon as you have a superuser app installed
So from the reactions i got (and I'll change the op until i got a new, good working version) root isn't working properly, but working nonetheless
Sent from my SGP521 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, and I'm not totally familiar with the way Sony has their kernel/boot image laid out. Different from other tablets I've worked on.
Will look into things though as time permits.
Moscow Desire said:
Naw, no offense taken. :highfive:
I hate unlocking mine as well, but eventually will probably have to. Just hate going through Sony to do it, as they will have my tab ID on record
Click to expand...
Click to collapse
Oh yeah, if you have made a backup of your TA you can safely re-lock your tab again without worrying about warranty. Because the DRM keys are in TA, and if you restore that (only if you backed it up prior to unlocking the first time) you also restore your drm keys
Tested to work when i had xperia T, with my current Z and a bunch of other Sony phones from friends
Even used warranty once after screwing things up i just restored TA, made it completely stock and went to the shop to claim my warranty
Sent from my SGP521 using XDA Premium HD app
Quick question: If the rom can't write to the system, can the recoveries? The only thing I need write access to the system partition is for changing the fonts and for the hosts file but I can do that in recovery. If that's the case I could live with root without full system access like in this rom.
crazymister said:
Oh yeah, if you have made a backup of your TA you can safely re-lock your tab again without worrying about warranty. Because the DRM keys are in TA, and if you restore that (only if you backed it up prior to unlocking the first time) you also restore your drm keys
Tested to work when i had xperia T, with my current Z and a bunch of other Sony phones from friends
Even used warranty once after screwing things up i just restored TA, made it completely stock and went to the shop to claim my warranty
Sent from my SGP521 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, had to use my other PC, but they are backed up.
Just info, should probably look at this;
http://forum.xda-developers.com/showthread.php?t=2699858
So seeing the kernel itself isn't being changed, it may work changing ramdisk only.
Moscow Desire said:
Yeah, had to use my other PC, but they are backed up.
Just info, should probably look at this;
http://forum.xda-developers.com/showthread.php?t=2699858
So seeing the kernel itself isn't being changed, it may work changing ramdisk only.
Click to expand...
Click to collapse
Nah that won't work. The only thing spoken of is how to extract boot.img from an ftf and how to inject that into your update.zip. As soon as you make even the tiniest change in kernel (ramdisk included) the kernel isn't signed anymore and you won't be able to flash it.
I have build my own rom in the past for xperia t, and i decided that learning to build your own rom and kernel at the same time is to much work
I will see what i can do later today, when my ex picks up my son I'll have some free time at hand then.
So to install Ubuntu and configure it to use it again. I hope i have something usefull tonight.
Sent from my SGP521 using XDA Premium HD app
in the kulverti thread 4.4.4 starts rolling out today he mentions some files that need modding in the recovery installer to kill sonyric so you can get rw system access . does that help ?
any fix of system rights?
Jeddix said:
Quick question: If the rom can't write to the system, can the recoveries? The only thing I need write access to the system partition is for changing the fonts and for the hosts file but I can do that in recovery. If that's the case I could live with root without full system access like in this rom.
Click to expand...
Click to collapse
I tried this rom, but I also got no full system access. So I couldn't apply the sd fix patch. But I do have regular root rights. Is there any way so far to get also write permissions in the system?
steff_1964 said:
I tried this rom, but I also got no full system access. So I couldn't apply the sd fix patch. But I do have regular root rights. Is there any way so far to get also write permissions in the system?
Click to expand...
Click to collapse
Well, if you want to unlock your bootloader it makes it easier
Basically I run a modified ramdisk with some of the security disabled and a different patched adbd binary, Fastboot flash the boot.img, Fastboot boot the current TWRP, exit out (it installs SuperSU and the binary automatically), then reboot. Have full system RW, exposed modules, greenify, etc.
It's sort of a round-about way of getting root and /system rw, but the selinux is a pain.
Still looking for available adbd binaries that also work and clean up all my ramdisk comments I don't need :laugh::laugh::laugh:
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
windraver said:
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
Click to expand...
Click to collapse
You will need a different kernel to work with a 5.1 or 5.0 system image. We cannot flash a kernel with this method yet just system images.
Right, so the only thing we can do are modified "roms" based on stock. Can't flash recovery or kernel since those are on separate partitions.
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
timmyk465 said:
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
Click to expand...
Click to collapse
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Ekkoria said:
Not going to work. You need to mount an ext4 image. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
I'd definitely be interested in a guide. I just wish there was a tool for windows that would work.
You can do it on windows but it's way easier on Linux.
I'm gonna get Linux back up and running and see what I can cook up.
Ekkoria said:
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
ntxct said:
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
Click to expand...
Click to collapse
Open your file manager as root, then open the file.
---------- Post added at 11:49 PM ---------- Previous post was at 11:44 PM ----------
I wrote up and posted a quick guide (which probably sucks) for this purpose.