Related
Hey guys, need some help with this one from some of you with more android/linux experience than me.
In my continuing quest to make Blackhole as customizable as possible I've been working on a way for users to easily install paid apps (legally downloaded of course), and stuff that I don't have available in rom manager in one easy step at the same time the rom is installed. In pursuit of this goal I've found that it's possible for the update-script file inside a clockworkmod zip to call a script in the zip as well. I've gotten it to say it's run the script, but it doesn't do what it's supposed to. here's what i've got:
#! /bin/
busybox cp /sdcard/app/* /system/app/
When I type the command into a terminal on the phone it works. When I open an adb shell and type "bash install.sh" it works. But when I get the update.zip to run the script, or run it in root explorer it just says it's run it, but doesn't do anything.
Is there something I'm missing about how to call the script? Do I need to somehow add the bash program to the zip file so it can run the script right? Has anyone ever done something like this who can point me in the right direction?
do you have an output you can show us?
Sent from my SCH-I500 using XDA App
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
wizang said:
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Click to expand...
Click to collapse
Could very well be, it's not showing me any output when i run it the two ways it doesn't work, just says it's been run.
vegittoss15 said:
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Click to expand...
Click to collapse
Haha, caught me. I was trying to remain incognito Yeah, i'll get 2.4 loaded back up on rom manager for you today. But if you flash 3.0 it will upgrade you to DL09 and the DJ05 kernels and modem are compatible, or at least no one i know of has had issues.
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
sdcard is mounted when you go to recovery, because it's got to access the update.zip file on it to install anything. I'll try your code, do you know what to put after SYSTEM: to make it go to the /app directory? thanks for the idea, it's a different way to go, i didn't think about the fact the update-script could access the device if you don't use the "package" tag.
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
dcow90 said:
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
Click to expand...
Click to collapse
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
Well I gave that a shot, and i think it could work, but the recovery wouldnt do it. it says "non-package source path not yet supported" good idea tho.
yutsoku said:
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
Click to expand...
Click to collapse
If you can that would be great.
n0yd said:
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
Click to expand...
Click to collapse
I spent a good bit of time searching and most of the scripts I found were much more complex than what i need, or were written to run on a computer, which i've already done.
sonofskywalker3 said:
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
Click to expand...
Click to collapse
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
jt1134 said:
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
sonofskywalker3 said:
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
Click to expand...
Click to collapse
#!/bin/sh for scripts in recovery. #!/system/bin/sh for scripts in android.
Sent from my SCH-I500 using XDA App
Hello to all in comunity.
Galaxy s has only 30MB of cache size. And this is bad because some apps on the market can't be installed, since market uses this cache partition for the downloads. Is there a way to increase this size or to symlink it on some bigger partition like /data or somewhere else?
Sent from my GT-I9000 using XDA App
Anybody? I heard that's a way to symlink cache anywhere else, but i can't do it, everytime i try a message saying "resource busy" or something like this appears on Terminal Emulator. I'm trying to symlink cache to /data.
Do you have ext4 lagfix enabled?
Sent from my GT-I9000 using XDA App
No. Do i need to enable it?
Sent from my GT-I9000 using XDA App
Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Sent from my Galaxy S/CM7 using XDA App
avary said:
Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Click to expand...
Click to collapse
And what version of speedmod are you using? I'm on K12-T 500Hz....if i enable ext4 lagfix on cache, will i get the 100MB too?
And also, were you using CM7 already?
Thanks!!
I tried to symlink the cache to a folder i created ala hardcore's suggestion (Thanks again hardcore!), but unfortunately I got the same sized partition as the original cache folder, which kinda makes sense. Hopefully Samsung or one of the guys on XDA (yeah, they'll probably get a fix out before Sammy does) will have a solution.
avary said:
Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Sent from my Galaxy S/CM7 using XDA App
Click to expand...
Click to collapse
I call bull****.
So there isn't a way to do it right now? I guess we need supercurio's or hardcore's help. Please people, help to contact them. Thx!!
Sent from my GT-I9000 using XDA App
I agree
snapper.fishes said:
I call bull****.
Click to expand...
Click to collapse
So do I. I tried using the latest speedmod, and no change. Think the only solution would be to have the cache size changed in the internals. Definitely out of my league; I don't want to try changing a setting and lose the use of my phone. Hopefully someone gets a fix in; battle bears is calling...
Definitely we need to move this thread to android development and see if someone there with enough skills can help us. I think it's an urgent problem. What about battle bears? And what if gameloft start to sell their games on android market now?
Sent from my GT-I9000 using XDA App
Thanks!!!!
gangpe said:
I tried to symlink the cache to a folder i created ala hardcore's suggestion (Thanks again hardcore!), but unfortunately I got the same sized partition as the original cache folder, which kinda makes sense. Hopefully Samsung or one of the guys on XDA (yeah, they'll probably get a fix out before Sammy does) will have a solution.
Click to expand...
Click to collapse
lucbl1 said:
Anybody? I heard that's a way to symlink cache anywhere else, but i can't do it, everytime i try a message saying "resource busy" or something like this appears on Terminal Emulator. I'm trying to symlink cache to /data.
Click to expand...
Click to collapse
How do you guys exactly try to symlink it? I guess more people could help out if they knew exactly what you are doing and what the error messages exactly say.
I'm not really interested in getting a bigger cache partition since I don't use really big apps, but this would probably be thay way I'd do it:
(you could type these command either through adb shell or directly on the device using a terminal emulator -- WARNING: these commands are not tested and may horribly break something)
Code:
mkdir /data/cache
busybox rm -rf /cache
busybox ln -s /data/cache /cache
shantzu said:
How do you guys exactly try to symlink it? I guess more people could help out if they knew exactly what you are doing and what the error messages exactly say.
I'm not really interested in getting a bigger cache partition since I don't use really big apps, but this would probably be thay way I'd do it:
(you could type these command either through adb shell or directly on the device using a terminal emulator -- WARNING: these commands are not tested and may horribly break something)
Code:
mkdir /data/cache
busybox rm -rf /cache
busybox ln -s /data/cache /cache
Click to expand...
Click to collapse
I was just using the same code you posted. But i think that for symlinking, /system and /data must be in Ext2/3 or 4 format, am i right? I'll be testing it in the weekend!
I mentioned this issue to supercurio who is looking into it.
Sent from my GT-I9000 using XDA App
lucbl1 said:
I was just using the same code you posted. But i think that for symlinking, /system and /data must be in Ext2/3 or 4 format, am i right? I'll be testing it in the weekend!
Click to expand...
Click to collapse
well, tbqh I didn't work much with RFS, so I am not sure if it supports symlinks, I guess it can't hurt to try though...
If it doesn't work on RFS you'd have to try some ext FS (ext2, ext4, whatever you prefer).
rlorange said:
I mentioned this issue to supercurio who is looking into it.
Click to expand...
Click to collapse
So maybe supercurio can fix it. Let's hope! Any news please report here.
Sent from my GT-I9000 using XDA App
Problem fixed on last speedmod kernel!
Sent from my GT-I9000 using XDA App
can someone plz help me? i got the problem and its rly annoying..i have 2.3.3 xxjvo with cf_root how do i fix this ****?!
romdroid. said:
can someone plz help me? i got the problem and its rly annoying..i have 2.3.3 xxjvo with cf_root how do i fix this ****?!
Click to expand...
Click to collapse
If rou are rooted just folow this commands in terminal...
su
mkdir /sdcard/tempcache
mount -o bind /sdcard/tempcache /cache
This is temporary, after reboot cache will return normal and you can delete tempcache in sdcard...
Cheers
Yeah, so that.
Ya its called mass storage mode.
LOL
Is that what you'd use if you wanted to make a tar of your setup?
The Root said:
Is that what you'd use if you wanted to make a tar of your setup?
Click to expand...
Click to collapse
Hmm...
Make a tar on the phone?
I guess you could system dump your setup?
Or stick all your mods in the rom flash like i do and then restore with titanium.
Sorry i couldn't help i was just joking around.
You can use adb to make direct, bit-for-bit copies of each partition using the dd command, I just can't remember the exact format of the command. But the phone doesn't have a built-in method to do the reverse of what download mode is used for (although I'm not sure what Odin's dump option does, sounds like the right idea but I've never seen a how-to, and, of course, we've always been advised to uncheck all but auto reboot)
Try a google search for "xda epic 4g" and keywords pertaining to making your own odin flashable (using xda as a keyword yields more results from the forum, and using google instead of xda search yields results that actually contain the key search terms, lol). I learned of this from a thread somewhere around here, just can't recall where. Oh, and maybe it would be better NOT to include Epic, I'm starting to doubt myself as to whether the thread was in our section... Hope that helps you find what you're looking for
Sent from my SPH-D700 using XDA App
There is a "kernel panic upload mode" that various Samsung devices can get trapped in after a kernel panic. I've not seen it happen on an Epic, but that's not what you're asking about.
You can dump the flash partitions using adb. It's best done in recovery with the file systems mounted read-only, to guarantee that they're in a consistent state. While you can do it from Android, inevitably changes (particularly to /data) will be made underneath you while dumping, which is bad for restoration.
Anyways, in order to make a proper dump you need a recovery that spawns the adbd service with either ro.secure=0 or ro.debuggable=1 set in default.prop. I think ClockworkMod does this, but it's been a long time since I used it.
Boot into recovery and connect your phone up to USB. Run "adb shell" and make sure you have a root shell ("#" prompt). If you have a user shell ("$" prompt), try running "adb root", wait, then run "adb shell" again. Once at the root shell prompt, run:
Code:
mount -ro remount /dev/block/stl6 /mnt/.lfs
mount -ro remount /dev/block/stl9 /system
mount -ro remount /dev/block/stl10 /data
mount -ro remount /dev/block/stl11 /cache
mount -t vfat /dev/block/mmcblk0p1 /sdcard
mkdir /sdcard/dump
cd /sdcard/dump
sync
cat /dev/block/bml1 > boot.bin
cat /dev/block/bml2 > ries.pit
cat /dev/block/bml4 > Sbl.bin
cat /dev/block/stl6 > param.lfs
cat /dev/block/bml7 > zImage
cat /dev/block/bml8 > recovery.bin
cat /dev/block/stl9 > factoryfs.rfs
cat /dev/block/stl10 > datafs.rfs
cat /dev/block/stl11 > cache.rfs
cd /
umount /sdcard
mount -wo remount /dev/block/stl6 /mnt/.lfs
That remounts all the stl partitions read-only, mounts the SD card, creates /sdcard/dump, dumps all the partitions, unmounts the SD card, and remounts /mnt/.lfs read-write so the phone will reboot properly. At this point you can reboot and once in Android, copy the dump folder over to a computer.
From here you can create a .tar containing the partitions that you want to flash with Odin/Heimdall. In Linux or Cygwin, that would be:
Code:
tar cf foo.tar zImage recovery.bin factoryfs.rfs datafs.rfs cache.rfs
.
You could include param.lfs, but it's not worth restoring unless corrupt, and if it's corrupt it's probably better to grab the version from the latest stock tar. I also wouldn't flash boot.bin or Sbl.bin unless you absolutely have to, and again, I'd go for the stock tar versions.
Also, according to the Galaxy S wiki page, bml12 is supposed to contain modem.bin but I've never had success dumping it.
Disclaimer: I've never actually restored a dump with Odin/Heimdall--I haven't had the need to. But I believe the above should be all that's necessary.
All hail mkasick! Thanks for my daily education
Sent from my SPH-D700 using xda premium
JohnCorleone said:
All hail mkasick! Thanks for my daily education
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I know understand you "ocean of knowledge" metaphor lol
Sent from my SPH-D700
Thanks guys.
whoa I just got edjumicated! that's some detailed info. thanks
Sent from my SPH-D700 using XDA App
I think it should be manditory for mkasick to post once a day minimum
Sent from my SPH-D710 using xda premium
JohnCorleone said:
I think it should be manditory for mkasick to post once a day minimum
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Agreed.
Posted by Mr. Z's Epic 4G Touch+Keyboard
Considering you can't dump the modem (with anything, bmlwrite, redbend_ua, dd) is it safe to assume you can't flash one to it?
remember to thank me if I was helpful
It might be possible to dump the modem, just not with the same method as regular flash partitions. But yes, I think all the modem image we have came from stock Odin tars.
As for flashing the modem, folks definitely do it with Odin. Samsung's recovery also contains a "write_firmware_image" function that a binary diff of the modem and applies it to the current firmware. It's not part of the AOSP recovery sources, so I don't know how it works.
Come to think of it, there's no obvious check to see if the modem is the correct version when applying an OTA update. So if you're running a stock phone except for the modem, and apply an update, something unfortunate might happen.
mkasick said:
It might be possible to dump the modem, just not with the same method as regular flash partitions. But yes, I think all the modem image we have came from stock Odin tars.
As for flashing the modem, folks definitely do it with Odin. Samsung's recovery also contains a "write_firmware_image" function that a binary diff of the modem and applies it to the current firmware. It's not part of the AOSP recovery sources, so I don't know how it works.
Come to think of it, there's no obvious check to see if the modem is the correct version when applying an OTA update. So if you're running a stock phone except for the modem, and apply an update, something unfortunate might happen.
Click to expand...
Click to collapse
I know you can flash with odin...I mean on-device (if thats a word?) tools. I started looking into the di18-ec05 update.zip. What is the difference between a modem.bin and modem_delta.bin? There seems to be a pretty hefty size difference
The delta contains just the diffs between modems.
mkasick said:
You can dump the flash partitions using adb. It's best done in recovery with the file systems mounted read-only, to guarantee that they're in a consistent state. While you can do it from Android, inevitably changes (particularly to /data) will be made underneath you while dumping, which is bad for restoration.
Click to expand...
Click to collapse
Yes, that was what I was thinking of - thanks for a *much* more detailed explanation, mkasick!
Sent from my SPH-D700 using XDA App
I posted a tutorial on how to mke an odin tar a loong time ago in general.. using dd instead of cat, same **** though...
Also modem patches are redbend bindifs full modems can't be flashed except in download mode.. they aren't actually in bml12, its some trickery involved, they are really in the nvram..
Also epic does have a kernel panic upload mode... little green guy and all, seen it a few times lol
Sent from my SPH-D700 using XDA App
mkasick said:
Come to think of it, there's no obvious check to see if the modem is the correct version when applying an OTA update. So if you're running a stock phone except for the modem, and apply an update, something unfortunate might happen.
Click to expand...
Click to collapse
There is an edify script assert for baseband version btw
Sent from my SPH-D700 using XDA App
Holy crap. I found upload mode. Kinda. Get your favorite file manger, and browse to /mnt/.lfs. TELL ME WHAT YOU SEE. Cuz I'm confused
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?
JakeDHS07 said:
Ok guys. I am gonna throw you all a bone here. Cause I'm nice like that. I haven't been able to figure out the bootloader but I have gained write protection off already.
Heres the process I used
go to play store and download an app called BusyBox Install (No Root) and install it and install BusyBox
If you don't already go and download Android Terminal Emulator from the play store
Now after you install emulator open and enter su
Accept the superuser prompt
now go back to the busybox app and copy the link it gives you and enter in emulator by pasting and hit enter
exit out of emulator
reopen emulator and ensure su is enabled by looking for the $
enter the following command busybox mount -o rw,remount system
Wait a minute or so
Reboot and profit!
Click to expand...
Click to collapse
Found this going through the turbo section, does anyone want to try this?
[email protected]:/ $ su
[email protected]:/ # busybox mount -o rw,remount system
tmp-mksh: busybox: can't execute: Permission denied
126|[email protected]:/ #
JH1108 said:
Found this going through the turbo section, does anyone want to try this?
Click to expand...
Click to collapse
It's not going to be anything as already stated. If it was that easy, it would've been done already.
Disable system write protection
Did anyone try to use this kernel extension to disable Write Protection?
carbonat87 said:
Did anyone try to use this kernel extension to disable Write Protection?
Click to expand...
Click to collapse
I doubt it that's for HTC one
Sent from my XT1080 using XDA Free mobile app
kalel420 said:
I doubt it that's for HTC one
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
And what? A didn't ask what for is that extension.
carbonat87 said:
And what? A didn't ask what for is that extension.
Click to expand...
Click to collapse
No you asked if anyone had tried it and I said I doubt it it's for HTC one kernel, but feel free to try that should give you a very nice brick I would think.
Sent from my XT1080 using XDA Free mobile app
kalel420 said:
No you asked if anyone had tried it and I said I doubt it it's for HTC one kernel, but feel free to try that should give you a very nice brick I would think.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Seems you don't know anything about bricks. In the worst way it will give a soft brick which is easy to repair. If you can't help with this, what are you doing here?
I'm asking this question because it can be done only on unlocked bootloader.
carbonat87 said:
I'm asking this question because it can be done only on unlocked bootloader.
Click to expand...
Click to collapse
What makes You think it is only for unlocked bootloader? Anyway if You had unlocked bootloader you would not need to turn WP off.
Do we actually have any knowledge on how the write-protection is done in our phones? Is it the same way as in htc? Do we have the kernel code for this to look at? I did see that motorola released some code because of the gpl license, but is it there?
So I did try this and no luck.
I took the latest sources from here:
https://github.com/flar2/wp_mod
I took the motorola kernel sources from here:
https://github.com/MotorolaMobilityLLC/kernel-msm
I compiled the module and copied it to the phone, but insmod did not work:
insmod init_module failed (operation not permitted)
I did run su in the console before trying the insmod. I have no idea why I can't insert the module into kernel, maybe it would have to be copied into /lib/modules/ and insmoded at boot, but that would require to burn the module into the system and flash it, but i have no time for that currently.
pizmak said:
So I did try this and no luck.
I took the latest sources from here:
https://github.com/flar2/wp_mod
I took the motorola kernel sources from here:
https://github.com/MotorolaMobilityLLC/kernel-msm
I compiled the module and copied it to the phone, but insmod did not work:
insmod init_module failed (operation not permitted)
I did run su in the console before trying the insmod. I have no idea why I can't insert the module into kernel, maybe it would have to be copied into /lib/modules/ and insmoded at boot, but that would require to burn the module into the system and flash it, but i have no time for that currently.
Click to expand...
Click to collapse
Ok, thanks for great work. I'll try to find someone who would be able to bake into system your compiled module and give us dump.
carbonat87 said:
Ok, thanks for great work. I'll try to find someone who would be able to bake into system your compiled module and give us dump.
Click to expand...
Click to collapse
Just be careful with this, because if the module gets insmoded correctly, but does not work with our kernel and cause a reboot it will leave you with a brick and you would have to flash the filesystem once again without this module burnt in.