Related
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
I just had an idea. What if someone roots a system.img by extracting it from a kdz and then mounting it in linux copying the root files setting the permissions and then flashing that with download mode? A simple
Code:
dd if=/data/local/tmp/system.img of=/dev/block/platform/??????/by-name/system
should do the trick to flash the system.img file replacing the ?????? with the correct directory.
Just a thought.
Wouldn't you have to have read/write access in order to push the system.img?
Impossible,without root.
Sent from my LG-D802 using Tapatalk
l33tlinuxh4x0r said:
I just had an idea. What if someone roots a system.img by extracting it from a kdz and then mounting it in linux copying the root files setting the permissions and then flashing that with download mode? A simple
Code:
dd if=/data/tmp/system.img of=/dev/block/platform/??????/by-name/system
should do the trick to flash the system.img file replacing the ?????? with the correct directory.
-
Click to expand...
Click to collapse
Dennisg34 said:
There's already a thread to discuss root. Please search before posting, thanks.
Sent from my G4 using your mom
Click to expand...
Click to collapse
I think both of the previous threads discussing root have been closed. I haven't seen another - did I miss it?
Already tried something similar. Requires root unless you're one of the lucky few who have such advanced knowledge of hacking bootloaders/exploits....which I unfortunately am not. LOL
rfarrah said:
I think both of the previous threads discussing root have been closed. I haven't seen another - did I miss it?
Click to expand...
Click to collapse
Apologies, I forgot they were.
Hello,
It is possible to rooter lg g4 with : V10B LGH815
thank you :fingers-crossed:
dydyfr said:
Hello,
It is possible to rooter lg g4 with : V10B LGH815
thank you :fingers-crossed:
Click to expand...
Click to collapse
Yes, look in the developer section.
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
l33tlinuxh4x0r said:
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
Click to expand...
Click to collapse
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
tabp0le said:
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
Click to expand...
Click to collapse
very true.
tabp0le said:
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
Click to expand...
Click to collapse
l33tlinuxh4x0r said:
very true.
Click to expand...
Click to collapse
Though...wouldn't it still be able to get into download mode? I could be wrong, but that's not on the system partition from my understanding.
I'm on linux and am familiar with dd (I'm a distro-hopper and have no optical drive, so everything gets dd'ed onto usb drive).
Wouldn't we have to specify a block size on that? I know at least on linux distro, if block size isn't specified, I end up in non-boot.
geoff5093 said:
Yes, look in the developer section.
Click to expand...
Click to collapse
Good
Thank's
Sent from my Iconia A3-A20 FHD using XDA Free mobile app
Th3Bill said:
Though...wouldn't it still be able to get into download mode? I could be wrong, but that's not on the system partition from my understanding.
I'm on linux and am familiar with dd (I'm a distro-hopper and have no optical drive, so everything gets dd'ed onto usb drive).
Wouldn't we have to specify a block size on that? I know at least on linux distro, if block size isn't specified, I end up in non-boot.
Click to expand...
Click to collapse
Actually you are correct. The laf partition is the download mode. Flashing recovery is where we have to worry about losing download mode. (I never understood why, but at least with the G2 download mode broke when flashing custom recovery without a certain patch)
The previous root threads were locked because peopel wouldn't stay on topic after multiple warnings...
Eagle1337 said:
The previous root threads were locked because peopel wouldn't stay on topic after multiple warnings...
Click to expand...
Click to collapse
Correction, they were closed per OP request
This one is now clean, lets try to stay on topic,
If anyone feels the urge to regurgitate further horse crap... we'll see what happens
l33tlinuxh4x0r said:
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
Click to expand...
Click to collapse
How can you confirm being able to dd to partitions using download mode? In download mode isn't the dd running from /system/bin that is mounted as ro. How could you replace /system while it is mounted and running dd from it?
gbgadgets said:
How can you confirm being able to dd to partitions using download mode? In download mode isn't the dd running from /system/bin that is mounted as ro. How could you replace /system while it is mounted and running dd from it?
Click to expand...
Click to collapse
linux loads commands that you are in the process of running into ram. You can even delete a file that you are running and still be able to use it until you close it. Once you close it is when the problem would occur but by that time you would already have the new file in place. Also do NOT run a
Code:
dd if=/dev/zero of=/dev/block/platform/??????/by-name/system
just skip that step otherwise you would lose the ability to dd.
Go directly for a
Code:
dd if=/data/local/tmp/system.img of=/dev/block/platform/??????/by-name/system
also to get a system.img instead of extracting from a kdz you could run
Code:
dd if=/dev/block/platform/??????/by-name/system of=/data/local/tmp/system.img
docfreed said:
Wouldn't you have to have read/write access in order to push the system.img?
Click to expand...
Click to collapse
you can push to /data/local/tmp using adb without root.
Came across this today. I didn't upload it, so thank you to whoever did!
http://www.filefactory.com/file/1bh0acofnjf9/XT1254_QUARK_VERIZON_5.1_SU3TL-38_38_CFC.xml.zip
btw, file factory is slow so be patient.
downloading. Will check the build prop and re upload to file hosts that aren't capped at 50 kb/s in ~7hrs
Found this last night and downloaded overnight.
MEGA mirror: https://mega.co.nz/#!XABCUAKQ!XMAKu5xHTEl06-nXHXUp-R4HrI3NvqfP28pP7dYeXMY
SHA1: e569e17cefe7045c3424a8aae8c7dc0c51f51202
I was able to convert the system.img_sparsechunks by doing:
Code:
simg2img system.img_sparsechunk* system.img.raw
dd if=system.img.raw ibs=2048 skip=64 of=system.img
truncate -s 3539992576 system.img
I don't have enough posts to create a development thread (I'm a quiet dev) but I'll post the stock image + a rooted image once I get it all working.
firstEncounter said:
Found this last night and downloaded overnight.
MEGA mirror: https://mega.co.nz/#!XABCUAKQ!XMAKu5xHTEl06-nXHXUp-R4HrI3NvqfP28pP7dYeXMY
SHA1: e569e17cefe7045c3424a8aae8c7dc0c51f51202
I was able to convert the system.img_sparsechunks by doing:
Code:
simg2img system.img_sparsechunk* system.img.raw
dd if=system.img.raw ibs=2048 skip=64 of=system.img
truncate -s 3539992576 system.img
I don't have enough posts to create a development thread (I'm a quiet dev) but I'll post the stock image + a rooted image once I get it all working.
Click to expand...
Click to collapse
Just FYI - there is a utility that will convert the sparse chunks to a single image ext4 system.img:
http://forum.xda-developers.com/showthread.php?t=2749797
http://forum.xda-developers.com/showpost.php?p=61132614&postcount=3
But there is likely a header and a footer in the file as explained in that thread. Those have to be removed using a HEX Editor before you can flash it using mofo.exe. I wrote out the instructions on how to do that in that thread above.
Then you can root it using @btdownloads7's method found here:
http://forum.xda-developers.com/showpost.php?p=61132621&postcount=4
No need to reinvent the wheel if you have a device running TWRP you can just follow that method.
We have also learned that you have to delete the contents of both /data/dalvik-cache and /cache before you flash an image with Xposed for Lollipop baked into it. This has to do with the conversion from dalvik to ART.
If you are having trouble getting Xposed baked into your image, you can read about @mikeoswego's method here but check to make sure you are using the most recent Xposed files as there have been updates:
http://forum.xda-developers.com/showpost.php?p=61132732&postcount=7
Where does one go about getting these Verizon images? Is it something Verizon issues to the public? If not, how does one trust this image as not being tampered with?
crackd said:
Where does one go about getting these Verizon images? Is it something Verizon issues to the public? If not, how does one trust this image as not being tampered with?
Click to expand...
Click to collapse
They cannot be tampered with, or they cannot be flashed through the signature check, which is what verifies the integrity of the file as well. Mofo, however, does not verify signature for obvious reasons. Where this particular file popped up is hard to say.
http://i.imgur.com/x1OUS1H.png
Working on uploading the images now.
I cannot thank you for this enough. I removed the erase USERDATA line, and I'm hoping that fixes my issue. cross your fingers.
firstEncounter said:
http://i.imgur.com/x1OUS1H.png
Working on uploading the images now.
Click to expand...
Click to collapse
So it worked?
Koneesha said:
So it worked?
Click to expand...
Click to collapse
It did, and we retain the ability to downgrade to 4.4.
firstEncounter said:
It did, and we retain the ability to downgrade to 4.4.
Click to expand...
Click to collapse
how big is the ext4 file?
JulesJam said:
how big is the ext4 file?
Click to expand...
Click to collapse
3376MiB (3539992576 bytes)
firstEncounter said:
http://i.imgur.com/x1OUS1H.png
Working on uploading the images now.
Click to expand...
Click to collapse
Very cool!
I have an XT1225 so root was easy, glad to see Turbo guys can have some fun too.
firstEncounter said:
http://i.imgur.com/x1OUS1H.png
Working on uploading the images now.
Click to expand...
Click to collapse
How did you do it? If it is possible more in detail?
ilia3367 said:
How did you do it? If it is possible more in detail?
Click to expand...
Click to collapse
I posted some more information in this thread, once I get everything settled root-wise and the images uploaded, I'll make a more detailed guide.
firstEncounter said:
Found this last night and downloaded overnight.
MEGA mirror: https://mega.co.nz/#!XABCUAKQ!XMAKu5xHTEl06-nXHXUp-R4HrI3NvqfP28pP7dYeXMY
SHA1: e569e17cefe7045c3424a8aae8c7dc0c51f51202
I was able to convert the system.img_sparsechunks by doing:
Code:
simg2img system.img_sparsechunk* system.img.raw
dd if=system.img.raw ibs=2048 skip=64 of=system.img
truncate -s 3539992576 system.img
I don't have enough posts to create a development thread (I'm a quiet dev) but I'll post the stock image + a rooted image once I get it all working.
Click to expand...
Click to collapse
OMG thanks! i will add it to the main firmware thread!!!!
Hi all I've read some guide to extract param.bin with terminal emulator but nothing work. Anyone give me the correct procedure to extract param.bin modify boot image and save it?
Thanks.
freejtd said:
Hi all I've read some guide to extract param.bin with terminal emulator but nothing work. Anyone give me the correct procedure to extract param.bin modify boot image and save it?
Thanks.
Click to expand...
Click to collapse
Maybe you are querying the wrong block. Try this :
Code:
su
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/param.bin
zlazaar said:
Maybe you are querying the wrong block. Try this :
Code:
su
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/param.bin
Click to expand...
Click to collapse
I've tried that block but it's 10mb
The dimension of param.bin it's about 1mb right?
P8 block is 530 kb
Really I don't know what is right block to export.
freejtd said:
Maybe you are querying the wrong block. Try this :
I've tried that block but it's 10mb
The dimension of param.bin it's about 1mb right?
P8 block is 530 kb
Really I don't know what is right block to export.
Click to expand...
Click to collapse
Size is different on each device.
On the S4 for exemple, it's about 4mb.
According to the stock partition table of N9005, param is located on 10th block.
Edit: you can also use ibs, obs or bs options of dd command to limit the size dumped from that partition.
The content never occupy the exact full size of a partition.
zlazaar said:
Size is different on each device.
On the S4 for exemple, it's about 4mb.
According to the stock partition table of N9005, param is located on 10th block.
Click to expand...
Click to collapse
Ok well I will try add new boot img in block p10. I've read a guide for note 4 but when launch tar command it give me error. I'm not expert, simply follow guide at letter.
Do you have another type of command to add new img on param.bin?
Thank you for reply at this thread it's most appreciated.
freejtd said:
Ok well I will try add new boot img in block p10. I've read a guide for note 4 but when launch tar command it give me error. I'm not expert, simply follow guide at letter.
Do you have another type of command to add new img on param.bin?
Thank you for reply at this thread it's most appreciated.
Click to expand...
Click to collapse
Can you please explain what do you want to do exactly.
The only boot.img i know is the kernel it self.
zlazaar said:
Can you please explain what do you want to do exactly.
The only boot.img i know is the kernel it self.
Click to expand...
Click to collapse
Just changing img note 3 with img note 7. When you boot device you see the name..
Look at this http://forum.xda-developers.com/note-4/themes-apps/tutorial-edit-note-4s-boot-splash-screen-t3223157
freejtd said:
Just changing img note 3 with img note 7. When you boot device you see the name..
Click to expand...
Click to collapse
The guide is very clear, use the provided script if needed.
Make sure you replace 08 by 10 in block name.
Your modified image must be =< 200kb and exactly 1920x1080px.
Sorry can't help more.
Thanks for your help.
I tried block p8 tar xf give me error.
freejtd said:
Thanks for your help.
I tried block p8 tar xf give me error.
Click to expand...
Click to collapse
Take a look here : http://forum.xda-developers.com/showpost.php?p=47675405&postcount=35
zlazaar said:
Take a look here : http://forum.xda-developers.com/showpost.php?p=47675405&postcount=35
Click to expand...
Click to collapse
Thank you I can't untar param.bin it give me error I think isn't my job :crying:
freejtd said:
Thank you I can't untar param.bin it give me error I think isn't my job :crying:
Click to expand...
Click to collapse
Install Busybox (if not already done) then use "busybox tar" instead of "tar"
zlazaar said:
Install Busybox (if not already done) then use "busybox tar" instead of "tar"
Click to expand...
Click to collapse
Installed busybox untar not working
Invalid tar format.
Ahhh my patience it's ended grrrr
ls -l /dev/block/platform/msm_sdcc.1/by-name
will show you the right block.
block 10 is right.
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
i pulled it and opened it in a hex editor. it's empty.
any more ideas?
I have no ideas. Just follow guide but nothing to do.
freejtd said:
I have no ideas. Just follow guide but nothing to do.
Click to expand...
Click to collapse
The last time I read in note 4 forum it's only for exynos.
Sent from my SM-G925F
Rosli59564 said:
The last time I read in note 4 forum it's only for exynos.
Sent from my SM-G925F
Click to expand...
Click to collapse
:crying:
@freejtd If I remember correctly, you once posted on Phronesis rom thread that you have the note 7 param.bin file. I would like to have that, I'm gonna try to edit Note 3 param.bin with Note 7. I'm also stuck a param.bin untar. I have no errors everything goes perfect but I get no images in param folder (strange). But I'm still trying and need note 7 param.bin
immi said:
@freejtd If I remember correctly, you once posted on Phronesis rom thread that you have the note 7 param.bin file. I would like to have that, I'm gonna try to edit Note 3 param.bin with Note 7. I'm also stuck a param.bin untar. I have no errors everything goes perfect but I get no images in param folder (strange). But I'm still trying and need note 7 param.bin
Click to expand...
Click to collapse
open param.bin with a hex editor. it's empty. this is why you don't get anything after untaring. logo must be located elsewhere i guess. but maybe param.bin from another model would be helpfull for finding the data we are looking for.
So I did the step to here.But do not know how to get system.img/boot.img/bootloader.img(most want).Any developers help?
jackzhu said:
So I did the step to here.But do not know how to get system.img/boot.img/bootloader.img(most want).Any developers help?
Click to expand...
Click to collapse
You could try this not sure if it work haven't tried yet use terminal emulator
Run this first and it will list your img you want
ls -al /dev/block/platform/soc/1da4000.usfhc/by-name
dd if=/dev/block/platform/soc/1da4000.ufshc/by-name (the img you want) of=/sdcard/ (your img)
You can use this command to dump any partition updated command
tattedup said:
You could try this not sure if it work haven't tried yet use terminal emulator
Run this first and it will list your img you want
ls -al /dev/block/platform/soc/1da4000.usfhc/by-name
dd if=/dev/block/platform/soc/1da4000.ufshc/by-name (the img you want) of=/sdcard/ (your img)
You can use this command to dump any partition updated command
Click to expand...
Click to collapse
You mean xxx_a.img is same as xxx_b.img?
jackzhu said:
You mean xxx_a.img is same as xxx_b.img?
Click to expand...
Click to collapse
If you flash the stock restore from invisiblek yes the a and b img should be the same, I think not positive not much knowledge on a and b partitions. But what I got from invisiblek's post is that is correct.
tattedup said:
If you flash the stock restore from invisiblek yes the a and b img should be the same, I think not positive not much knowledge on a and b partitions. But what I got from invisiblek's post is that is correct.
Click to expand...
Click to collapse
Thank you, I will dump it for try .
jackzhu said:
Thank you, I will dump it for try .
Click to expand...
Click to collapse
I'm sure I get the boot.img. do you know which is/are bootloader.img?