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
I could not find any binaries of the MTD-Utils (a set of useful tools when dealing with flash devices; see http://www.linux-mtd.infradead.org/index.html) for Android so I compiled some Android binaries from the source (http://git.infradead.org/mtd-utils.git).
My main interest was to get the two programs 'nanddump' and 'nandwrite' running on Android which must be used instead of 'dd' when creating images of nand partitions and restoring partitions from these images, because dd does not handle the bad blocks on the nand correctly which could lead to corrupted data.
With these two tools more flexible backup/recovery tools can be implemented since a backup/recovery can be made for every partition available on the device, even those which do not have a readable filesystem, for example the bootloader. Also, for partitions which include a filesystem, but hide some extra data outside that filesystem, this hidden data will also be included in the backup. These raw nand partition images can be tar'd or zip'd to reduce the size of the backup files.
Download: http://www.multiupload.com/5GJLEJNR8M
I do not accept donations, however if you want to make my life easier and thank me for my efforts, please think about signing up for a free SpiderOak account using this refer-a-friend link https://spideroak.com/download/referral/b89974e492728fa6a246880f0b7cbcd5. It is just like Dropbox except you can get up to 50GB of free space and they have a true zero-knowledge policy.
Thanks. I am trying to dump the system partition and restore it to another Android Mobile. Any Hints ? Thanks.
kkkelvinkk said:
Thanks. I am trying to dump the system partition and restore it to another Android Mobile. Any Hints ? Thanks.
Click to expand...
Click to collapse
Dump from one device wont work on other, if they are very similar it has few chances of booting but else it'ld brick if you dont be safe!
Actually, I want to remove some system app and then install other app, and make all configuration. After that, I want to clone this configuration to other mobile device with same model. Do you have any suggestions ?
Thanks.
kkkelvinkk said:
Actually, I want to remove some system app and then install other app, and make all configuration. After that, I want to clone this configuration to other mobile device with same model. Do you have any suggestions ?
Thanks.
Click to expand...
Click to collapse
Ok so you got a phone (model a) and you wanna remove sumtin frm /system/app n add sumtin back n then let some user having the same model a use it
Get root
Install root explorer or any root file explorer
Allow su permissions
Navigate to /system/app and do what you wanted
Then you can dump the /system partition
Kindly give some more info of your device - will help more
And yes also paste the output of "mount" command
I think I can only give more information about the phone after I back to my office.
Actually, I am using System App Remover to remove the System App. It does the job.
Wow can I dump and restore the system partition ? I have tried to use dd command, but it fails. May be nanddump will help, but I cannot find the documentation how to use it. Please help. Thanks.
Is there any way to have nanddump directly send the image to a PC that is running recv_image? I'd like to use nanddump on my Galaxy Nexus, but since it is lacking an SD card, it would seem like writing the nanddump image to the nand would just destroy any possibility of obtaining a clean nand image.
I found a way using netcat...
From host machine in one console window:
Code:
adb.exe forward tcp:5555 tcp:5555
adb.exe shell
# nanddump [options] /dev/mtd/mtd0 | nc -l -p 5555
From host machine in a second console window
Code:
nc 127.0.0.1 5555 > flashdump.bin
So how does nanddump compare with Nandroid, which uses mkyaffs2image to create .img files?
So does n e one a mirror for this??? Multiupload is no good n e more...
Sent from my Hellfire Kindle using xda premium
da-pharoah said:
So does n e one a mirror for this??? Multiupload is no good n e more...
Sent from my Hellfire Kindle using xda premium
Click to expand...
Click to collapse
Per my request, stericson kindly built nanddump and nandwrite into his version of busybox. If you still want Ezekeels's pack, I might still have it around here somewhere.
Maximilian Mary said:
Per my request, stericson kindly built nanddump and nandwrite into his version of busybox. If you still want Ezekeels's pack, I might still have it around here somewhere.
Click to expand...
Click to collapse
Yes please and thank you..
Sent from my Hellfire Kindle using xda premium
da-pharoah said:
Yes please and thank you..
Sent from my Hellfire Kindle using xda premium
Click to expand...
Click to collapse
Nope. I dug through my sdcard and the backups on my computer, and I do not still have it. If you want to contact the OP directly, he is @ezekeel666 on twitter.
Maximilian Mary said:
Nope. I dug through my sdcard and the backups on my computer, and I do not still have it. If you want to contact the OP directly, he is @ezekeel666 on twitter.
Click to expand...
Click to collapse
dirty... and nope also.. I PM'd him and he informed me he deleted all his backups on this....
also try compile, but it hard for me.
all link dead. please, upload mtdutil again.
so I saw that you updated your github!! thanks! now lets see if I can get this sorted and btw if I end up using anything no worries I will give you full credit as usual! Thanks again!
mtd ultil for android
ok guys...
1st: sorry for reviving this topic ...
2nd:here ara the binaries for android: http://goo.gl/eJ8mX
3rd and most importanto to me:
If I do a nandread mtd7 > mtd7.img (in my case the /misc partition) I can do a nandwrite mtd7.img > /dev/mtd/mtd7 without any data corruption ?
I have a lot of backups of many partition except this /misc that in freaking me!
So. Is this a reliablbe backup/restore system ? can I do it with all mtd partition ?
* I tested nandread in qcom msm_7x27 device running android 2.3.6.
shaunco said:
I found a way using netcat...
From host machine in one console window:
Code:
adb.exe forward tcp:5555 tcp:5555
adb.exe shell
# nanddump [options] /dev/mtd/mtd0 | nc -l -p 5555
From host machine in a second console window
Code:
nc 127.0.0.1 5555 > flashdump.bin
Click to expand...
Click to collapse
Or just:
adb shell "nanddump -f - /dev/mtd/mtd0" > mtd0.img
-f - outputs to stdout
Excude the partial OT, but are there any similar tools for MMC flash storage?
Thread closed.
Thread closed.
Yank555 said:
Hi,
REMEMBER
FIRST OF ALL, do a Nandroid backup, as well as a backup of your sd-card content !
You're doing this at your very own risk, I'm not to be held responsible if something goes wrong
Now that said, let's get going
In case somebody wants to check it out, here is the swap activation script I wrote (attached) as well as explanations on how to make it all work :
1) Partition your sd-card (Minitool Partition Wizard, 4ext, CWM...)
2) Boot your system with the partitionned sd-card
3) If necessary customize the 99swap script (attached to this post) and then put it onto your sd-card's root folder, you'll need it while executing the commands in step 4.
4) Open a terminal and type the following
NB: Change "mkswap /dev/block/mmcblk0p3" accordingly to point to the swap partition you've created in step 1.
5) Reboot your phone, start a terminal again and type free, you'll need to see something different than 0 in your swap line, look at the attached print-screen
Swappiness will be set to 50 by the script, which is a rather conservative swap use, made sense to me since SD-swap is slower than ram, better not to use it too agressively. Feel free to experiment with the swappiness variable in the script (values between 0 and 100, 0 meaning "try not to swap", 100 meaning "try to swap all the time")
If you want to try and have a question, just let me know !
JP.
PS: You can find the thread for hard swap for the htc Sensation / XE here.
Click to expand...
Click to collapse
Hi JP,
This is a gem of a post! Thanks alot for the script and the detailed breakdown. Before I get into it though, I must warn you that I am more of a beginner with no coding/scripting experience (I don't know how to use adb or anything)...
Here's what I'm trying to do: I'm trying to activate hard-swap on my hd2 (currently) running the ParanoidAndroid by Xylograph. I've created 3 partitions on my 16gb class 6 sd card: first, fat32 (32k cluster), next, 1GB ext2 (default), 500MB swap.
Procedure:
1. I extracted the script and copied it directly to system/etc/init.d folder of the Rom (I looked at the terminal commands you posted and the first few lines looked like copying the file from the sd root to the init.d folder (it was just a guess though), so I figured might as well put it into the rom before I flash it)
2. Flashed the rom
3. To activate it, I typed the following into the terminal:
su
mount -o remount,rw /system
mkswap /dev/block/mmcblk0p3
mount -o remount,ro /system
exit
after the mkswap command, I did get an activation notification that a certain amount was assigned to swap. But my celebrations were cut short after I rebooted and used the free command to check. The entire swap row still read 0.
I was wondering if you can point me in the right direction... thanks!
Also, is there a way to create a cwm flashable version?
bullcrapr said:
Hi JP,
This is a gem of a post! Thanks alot for the script and the detailed breakdown. Before I get into it though, I must warn you that I am more of a beginner with no coding/scripting experience (I don't know how to use adb or anything)...
Here's what I'm trying to do: I'm trying to activate hard-swap on my hd2 (currently) running the ParanoidAndroid by Xylograph. I've created 3 partitions on my 16gb class 6 sd card: first, fat32 (32k cluster), next, 1GB ext2 (default), 500MB swap.
Procedure:
1. I extracted the script and copied it directly to system/etc/init.d folder of the Rom (I looked at the terminal commands you posted and the first few lines looked like copying the file from the sd root to the init.d folder (it was just a guess though), so I figured might as well put it into the rom before I flash it)
2. Flashed the rom
3. To activate it, I typed the following into the terminal:
su
mount -o remount,rw /system
mkswap /dev/block/mmcblk0p3
mount -o remount,ro /system
exit
after the mkswap command, I did get an activation notification that a certain amount was assigned to swap. But my celebrations were cut short after I rebooted and used the free command to check. The entire swap row still read 0.
I was wondering if you can point me in the right direction... thanks!
Also, is there a way to create a cwm flashable version?
Click to expand...
Click to collapse
Thanx
In fact you understood correctly that is was about copying the file to init.d.
By the way, these commands do the following :
mount -o remount,rw /system - Mount system partition in read-write
mount -o remount,ro /system - Mount system partition in read-only
So to format the swap partition "mkswap /dev/block/mmcblk0p3" there was no need for it, but it didn't harm in any way, so you're fine there
I guess what is missing is the "chmod 755 /system/etc/init.d/99swap" command which will set the correct file access to the script so it can get executed at boot.
You might do the following in a terminal :
su
mount -o remount,rw /system
chmod 755 /system/etc/init.d/99swap
mount -o remount,ro /system
exit
It should be fine then.
Alternatively you could set the rights with your file explorer (in root explorer mode), they must be "rwxr-xr-x" (which is Read-Write-Execute, Read-Execute, Read-Execute), most file-manager will allow you to do that as well.
I've been working on the script variant for htc Sensation, it is more advanced, dynamic so it can find the swap partition by itself.
I'll make a CWM flashable as soon as I get to it that will handle everything except partitioning the SD card, obviously, for both devices.
As soon as I'm done I'll post the HD2 version here as well (very little change, between both devices, just the access path to the sd-card partitons to change (=1 line in the script).
JP.
Edit ------------------------------------------------
I just reread your post, if in fact you put it into the ROM zipfile, then file access should be correct !?
Could you post the following file (if it exists) :
/data/swap.0.log ?
JP.
Yank555 said:
Thanx
In fact you understood correctly that is was about copying the file to init.d.
By the way, these commands do the following :
mount -o remount,rw /system - Mount system partition in read-write
mount -o remount,ro /system - Mount system partition in read-only
So to format the swap partition "mkswap /dev/block/mmcblk0p3" there was no need for it, but it didn't harm in any way, so you're fine there
I guess what is missing is the "chmod 755 /system/etc/init.d/99swap" command which will set the correct file access to the script so it can get executed at boot.
You might do the following in a terminal :
su
mount -o remount,rw /system
chmod 755 /system/etc/init.d/99swap
mount -o remount,ro /system
exit
It should be fine then.
Alternatively you could set the rights with your file explorer (in root explorer mode), they must be "rwxr-xr-x" (which is Read-Write-Execute, Read-Execute, Read-Execute), most file-manager will allow you to do that as well.
I've been working on the script variant for htc Sensation, it is more advanced, dynamic so it can find the swap partition by itself.
I'll make a CWM flashable as soon as I get to it that will handle everything except partitioning the SD card, obviously, for both devices.
As soon as I'm done I'll post the HD2 version here as well (very little change, between both devices, just the access path to the sd-card partitons to change (=1 line in the script).
JP.
Edit ------------------------------------------------
I just reread your post, if in fact you put it into the ROM zipfile, then file access should be correct !?
Could you post the following file (if it exists) :
/data/swap.0.log ?
JP.
Click to expand...
Click to collapse
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?
bullcrapr said:
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?
Click to expand...
Click to collapse
Hi,
You're welcome
The file '/data/swap.0.log' is a text-file containing info on the execution of the script...
If it's not there, then the script didn't run at all...
I should have a little time later today, will try to make the CWM flashable solution for you, should be a no fuss solution, as long as the sd-card has a swap partition
How did you partition the card ? CWM ?
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium
I created a 256Gb partition...
Click to expand...
Click to collapse
man thats a helluva sd card ya have there! hehe.
samsamuel said:
man thats a helluva sd card ya have there! hehe.
Click to expand...
Click to collapse
Haha I noticed that too :') I want one of those now
Nigeldg said:
Haha I noticed that too :') I want one of those now
Click to expand...
Click to collapse
Thanx for pointing that out Mb of course, but in a few years that might be possible
My first hdd had 60Mb, and that's not soooo long ago
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium
heh, my first was a 20mb HDD mounted on a pcb card and plugged into an ISA slot, took up the full length of the PC, weighed LOADS, could have beaten burglars to death with it.
bullcrapr said:
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?
Click to expand...
Click to collapse
+1 with this (also on Paranoid Rom 1.1a) but I think that it's something with the ROM coz on earlier build v1 this method worked verry good I hope that Yank will find a solution coz it reallly helps wit our 576 ram
samsamuel said:
heh, my first was a 20mb HDD mounted on a pcb card and plugged into an ISA slot, took up the full length of the PC, weighed LOADS, could have beaten burglars to death with it.
Click to expand...
Click to collapse
Mine was huge at the time, was on of the first to have such a big one, even partitioned it into 3 since it was just too big And it was an external device, the size of a pizza-box (it was en Atari Megafile 60, I still have it !!).
triggaz said:
+1 with this (also on Paranoid Rom 1.1a) but I think that it's something with the ROM coz on earlier build v1 this method worked verry good I hope that Yank will find a solution coz it reallly helps wit our 576 ram
Click to expand...
Click to collapse
I'm working on the CWM flashable right now, should be done within 1-2 hours at most
Yank555 said:
Hi,
You're welcome
The file '/data/swap.0.log' is a text-file containing info on the execution of the script...
If it's not there, then the script didn't run at all...
I should have a little time later today, will try to make the CWM flashable solution for you, should be a no fuss solution, as long as the sd-card has a swap partition
How did you partition the card ? CWM ?
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium
Click to expand...
Click to collapse
Hi JP, once you told me it was the address to the file, i just navigated there using my explorer and lo and behold!, there it was (attached). If you must know, in my earlier post, the idiot in me just typed it in the terminal and the terminal replied not found.
I made my partition using freeware called Minitool partition wizard. Is 500mb too big for swap in your opinion? I was thinking of compensating for zram, and hence the size... thanks for your speedy responses...
edit...
and hey! whadya know? in the meantime, this place is coming alive!!
bullcrapr said:
Hi JP, once you told me it was the address to the file, i just navigated there using my explorer and lo and behold!, there it was (attached). If you must know, in my earlier post, the idiot in me just typed it in the terminal and the terminal replied not found.
I made my partition using freeware called Minitool partition wizard. Is 500mb too big for swap in your opinion? I was thinking of compensating for zram, and hence the size... thanks for your speedy responses...
edit...
and hey! whadya know? in the meantime, this place is coming alive!!
Click to expand...
Click to collapse
Hmm ... strange, the content of the file looks like a logcat ?! Not what I was expecting to see
Give me a little hour, and I think I should be done with the flashable hard-swap and we'll go from there
Minitool is excellent, but did you pay attention to only create "primary" partition ? If it is a logical partition it won't work...
Can you insert your SD card into your card reader, start Minitool an post a print screen of it ?
JP.
EDIT :
About size ... I believe 256Mb is enough, even read somewhere t shouldn't be more than 256, but I think there was no specific reason given.
Yank555 said:
Hmm ... strange, the content of the file looks like a logcat ?! Not what I was expecting to see
Give me a little hour, and I think I should be done with the flashable hard-swap and we'll go from there
Minitool is excellent, but did you pay attention to only create "primary" partition ? If it is a logical partition it won't work...
Can you insert your SD card into your card reader, start Minitool an post a print screen of it ?
JP.
EDIT :
About size ... I believe 256Mb is enough, even read somewhere t shouldn't be more than 256, but I think there was no specific reason given.
Click to expand...
Click to collapse
Here we go...
Minitool image attached... I typically pay attention to the partition type and made sure both of them were primary
About the logcat, I suspect you're right... I was trying to do one from my pc for the first time using adb and tried the only few commands I know (mkswap...), I think that's what you saw then...
Incidentally, do you feel if I reduce the swap size, the script has a better chance at surviving the boot?
bullcrapr said:
Here we go...
Minitool image attached... I typically pay attention to the partition type and made sure both of them were primary
About the logcat, I suspect you're right... I was trying to do one from my pc for the first time using adb and tried the only few commands I know (mkswap...), I think that's what you saw then...
Incidentally, do you feel if I reduce the swap size, the script has a better chance at surviving the boot?
Click to expand...
Click to collapse
Don't bother, I will test 500Mb and let you know if that is the issue
JP.
I have 512mb partition and it worked without problems as I mentioned earlier so I think that opposite to the "size does matter" in this case it doesn't plus I used it with zram from marc1706.
triggaz said:
I have 512mb partition and it worked without problems as I mentioned earlier so I think that opposite to the "size does matter" in this case it doesn't plus I used it with zram from marc1706.
Click to expand...
Click to collapse
Hi triggaz, are you using the built in zram on Para1.1a? Or have you applied a script from elsewhere? I enabled the built-in zram, but get a "not found" reply when i try zram_stats in the terminal. Can you tell me how you got zram working? thanks...
bullcrapr said:
Hi triggaz, are you using the built in zram on Para1.1a? Or have you applied a script from elsewhere? I enabled the built-in zram, but get a "not found" reply when i try zram_stats in the terminal. Can you tell me how you got zram working? thanks...
Click to expand...
Click to collapse
https://www.dropbox.com/s/xr3z102gxiw2f62/marc1706_zram_100MB.zip
all credits to Dorimanx for ZRAM mod and mark1706 for modifications
I flashed this and then used the compcashe options in Paranoid (set to 26%)
ok so first boot into recovery make a nandroid than remove your external sdcard and download the odin flashible semaphore kernel for vibrant from semaphore.gr (be sure its the newest one) now go to download mode and flash that. as soon as its done it will reboot and you want to reboot into recovery. next plug it into your pc while still in recovery mode and run the adb devices command to be sure your devie is connected and recognized now go to adb shell and run these commands hitting enter after each line
parted /dev/block/mmcblk0
print
rm 1
rm 2
and what that does is removes all your partitions so just do rm X for each partition number you have puting a space between rm and whatever number you have. now go back to download mode and flash Eugene_2E_JK2_Froyo.tar heres a link to download http://d-h.st/VGX. and your going to go through the process of everything flashing in oden. besure to flash that as pda. than you will be at stock recovery and you will get the ant mount bla bla bla or if it boots straight to the rom to thats fine. and now go to settings and format internal sdard under storage settings your external sdcard should still be REMOVED now after thats done reboot and you should have a fully working vibrant. this fixed mine. if it doesnt work tell me hope i helped
also works with captivate and facinate too!!
First and foremost, thanks for posting this guide.
I'm gonna' run through this right now. Wish me luck. :fingers-crossed:
if it doesnt work tell me
N00B_IN_N33D said:
First and foremost, thanks for posting this guide.
I'm gonna' run through this right now. Wish me luck. :fingers-crossed:
Click to expand...
Click to collapse
if it doesnt worl tell me
Would it sound messed up if I wanted to EU my phone just to try this lol nice find C looks like a really nice guide
Sent from my Nexus 7 using xda app-developers app
Not 100% working yet sorry people
But im putting alot of work into it.
Sent from my SGH-T959 using xda premium
LOL
So I attempted your guide...and the good news is that i was able to access recovery right after flashing the sephamore kernel .tar in odin. The bad news on the other hand is that I was unable to execute the adb shell commands you've listed in your guide. I got an error stating that "there is no such file or directory". So I skipped the commands and flashed ICS passion v13 and it booted!!! but only to be followed by the dreadful "Encryption Unsuccessful" screen lol.
I took a screenshot of the EU screen by pressing the power button hoping to upload it here for you guys to see...but this is where things got really strange. So I removed the battery, sdcard, and inserted the sdcard into my pc to look for the screenshot and it wasn't there!!!. So this means that the screenshot was saved to the internal memory. I can sense I am getting closer to fixing my old vibrant.
Stay tuned
Like Merio I, too, flashed the Semaphore kernel via ODIN.
But unlike him, I cannot access Recovery.
fham said:
Like Merio I, too, flashed the Semaphore kernel via ODIN.
But unlike him, I cannot access Recovery.
Click to expand...
Click to collapse
Try the following commands in adb.
adb devices
adb remount (might fail but don't worry)
adb reboot recovery
i use devil kernel to access the recovery.....but at 'parted /dev/block/mmcblk0' this step i got the same as merio90
Yeah devil or semaphore. Semaphore is just easer to boot to recovery
Sent from my SGH-T959 using xda premium
Update
Well after 5+ hours of countless rebooting and flashing/modding I have failed to bring my vibrant back to life. However... I was able to go real deep into the device's storage hardware both internal and external(sdcard) and discovered that the internal storage is alive and functioning. In other words it is not hardbricked or physically damaged as a result of the EU bug...it is just corrupted and unable to mount.
Furthermore I attempted several times to create or recreate the partions on the internal sdcard but It just would not allow me to do so. By the way this is all done using the "parted /dev/block/mmcblk0" command(s). Hopefully there is some one who understands how to use this "parted" function in adb as this can be a very useful tool in restoring our devices back to normal.
Here are some helpful details I have learned in the process of all of this...
For those who are having trouble entering the commands in the guide make sure you are entering a space in between "parted" and "/dev/..."
At first I forgot to enter the space and as a result I got an error reading "no such file or directory" so make sure to include the space.
adb shell >>>>>>>>>>> Don't forget to enter this command first...won't work otherwise.
parted /dev/block/mmcblk0 >>>>>>> mmcblk0 is the external sdcard (at least in my case it is) while mmcblk0p1 is the internal sdcard (in my case)
print >>>>>>>> This command list the specifications for the storage device mmcblk0 along with some other useful information.
rm 1 >>>>>>>> This removes partition 1
rm 2 >>>>>>>> This removes partition 2 (if existent)
While still using the "parted" function in adb shell you can simply type "help" and it will give you all the details on how to use this useful tool.
Well I guess that is all I can say for now. Thanks again cannondale...your guide was certainly helpful and allowed me to learn more about this EU bug and how it is "bricking" our devices. This is certainly a step forward in the right direction...I am confident we will have this EU bug squashed pretty soon once and for all.
signing off.
@merio90 i did a lot of research on the EU BUG read my thread.... http://forum.xda-developers.com/showthread.php?t=2176108
manu_ha2001 said:
@merio90 i did a lot of research on the EU BUG read my thread.... http://forum.xda-developers.com/showthread.php?t=2176108
Click to expand...
Click to collapse
Thanks manu...this isn't the first time I've read your thread concerning the EU bug. I simply ignored it at first because it seemed a bit too technical at the time. But now that I've gone through this guide cannondale has provided your thread certainly makes more sense. I'll get back to working on this case soon.
So has anyone besides the OP gotten this to work?
well cannondale has
Merio90 said:
... This is certainly a step forward in the right direction...I am confident we will have this EU bug squashed pretty soon once and for all.
Click to expand...
Click to collapse
@Merio90 ... Just wondering if you made any further progress on the matter. Thanks to cannondaleV2000 for opening these doors and to Merio90 for the detailed posts (esp. concerning syntax). Very interesting thread.
I gave it a go but no nookie for me. In a nutshell, GNU Parted only appears to work on the external sdcard (mmcblk0p1) and not on the internal. Here are my results (after numerous attempts).
RECOVERY ACCESS
My observations flashing Semaphore JB .tar's (after a fresh Odin to Eugene_2E_JK2_Froyo.tar).
* Hangs on Semaphore splash: 2.9.21v, 2.9.15sv, 2.9.12sv.
* Recovery access successful: 2.9.21sv, 2.6.5v, 2.5.0sv
EXTERNAL SD REMOVED:adb shell
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
adb shell
# parted /dev/block/mmcblk0p1
parted /dev/block/mmcblk0p1
Error: Could not stat device /dev/block/mmcblk0p1 - No such file or directory.EXTERNAL SD INSERTED:adb shell
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
adb shell
# parted /dev/block/mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.So ... it's rather curious that cannondaleV2000 actually had access to his mmcblk0 while others weren't so lucky. That's the obvious key to using the parted functionality on the internal sdcard. If only we could break through that road block ... and return to the internal sdcard holy grail!! Any thoughts?
@yosup
No I have not made any progress other than the info I have already posted. My vibrant is no longer my daily driver, my Galaxy Nexus is... so my apologies for not giving this issue a higher priority.
I was only able to "fix" my vibrant to the point where I was able to use the SD card swap method many of us have attempted. In case you were unaware I had to take some extra steps as my vibrant was totally screwed up. It was unable to read either internal or external sdcard so that was an obstacle I had to overcome and that's how cannondale's guide was able to help me. So as of today no progress has been made...I haven't really worked on this problem in quite a while now so any progress has come to a halt for now...until someone comes up with a new guide On another note, the good news is that I have yet to encounter the EU bug on JB 4.2.2 (AOKP M1). So those who are using the sdcard swap method you should try a JB ROM...they seem to not be vulnerable to this EU bug.
Sent from my Galaxy Nexus using xda app-developers app
Try this
http://forum.xda-developers.com/showthread.php?p=44794873
Sent from my GT-I9505 using xda premium
<RESOLVED> [HELP]N7100_IMEI 0049xx_SN 0000.._Service State "out of service"
Hi Guys. I got this issue after upgrading my Note II to the latest OMEGA ROM v17. After doing the upgrade I was able to use it for a couple of hours and then I realized though there is a signal I am not receiving any internet data (internet icon was gone). I restarted the phone, switch to flight mode back and forth, switch on/off data, but still no luck. I soon realized also that I am not receiving any SMS or call. I thought it was just my carrier so I called them and made a complaint like hell. They said that my line should be fine. From there I started reading for all possible reasons why I am getting this issue. I then found out that my IMEI that is showing on the phone is different on the sticker attached on the battery compartment. Serial number on the phone is 000000000. Service state is "Out of service" though it detects from which network my SIM is. I have tried to flash different custom ROMs and several stock ROMs, but with no go. Tried also different methods on restoring EFS and still no luck. Stupid me, I don't have any backup EFS file or a copy of a nand backup. I was able to get out of the factory mode, wifi and everything else are working except for not receiving any call or SMS because of the bad IMEI, SN, and the Service state "Out of service". I have read some fixes on other threads from a different android phones, but with no avail in fixing mine. I know there's a lot of thread of the same issue, but I want to create my own so I can make sure that people who got ideas on how to fix this is just referring to my "own" issue which will be easier for me to monitor the thread.
So I have tried the following:
- flashed different custom ROMs - no good
- flashed several stock ROMs - no good
- tried EFS Professional.exe - no good
- tried N7100_EFS_Backup_Restore_WIN - no good
- tried ARIZAPatch.apk - no good
- tried SGS tools - no good
- tried com.helroz.GSII_Repair_102.apk - no good
- tried NV-items_reader_writer.exe - I don't know how to make it work
- restored old EFS Backup - no good
- able to find an old NANDroid backup (when it was still working before), flashed it - no good
They say helps the modem from the topic http://forum.xda-developers.com/showthread.php?t=2333216
### --- XXDME4 modem --- ### fix IMEI - -unknown modem
on the XXDME6 base - you can not install old modems,
because it will cause for unknown modem & imei status.
Solution flash - XXDME4 modem
XXDME4 modem
flash via TWRP / CWM
ATTACHED FILES
modem XXDME4 .zip - [Click for QR Code] (4.84 MB, 1209 views)
Click to expand...
Click to collapse
tried that still no go
red_hanks said:
...
Click to expand...
Click to collapse
Read this
victorator said:
Read this
Click to expand...
Click to collapse
Tried that mate but no luck.
in /efs folder contains files *.bak?
aaleo said:
in /efs folder contains files *.bak?
Click to expand...
Click to collapse
yup
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
aaleo said:
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
Click to expand...
Click to collapse
I have tried that method but it just made my note2 switch to factory mode. Sorry to ask but have you tried that method on your own or you just copy pasted that from somewhere showing that you're willing to help but no certainty if that really works or will just mess up something?
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
aaleo said:
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
Click to expand...
Click to collapse
Just tried original firmware but same thing. I am getting frustrated now..
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
aaleo said:
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
Click to expand...
Click to collapse
SIM card is ok. Read my explanation on post #1.
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
red_hanks said:
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
red_hanks said:
Tried that mate but no luck.
Click to expand...
Click to collapse
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Wow sounds complicated lol hope this don't happen to me!
Sent from my GT-N7100 using xda app-developers app
glevitan said:
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
Click to expand...
Click to collapse
Done with this with no luck.
aspot72 said:
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Not sure how to do that, never use Kies before
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Like what I have said, found an old backup of mine and it doesn't work. So it's pointless to try this.
I was sleepless (haha) trying to find solution for this. I came across this site and tried the app there. But as you can see on the image below, the button to change the IMEI is grayed out. There is not clear instructions on the site so it is kinda hard what to do in times like that. The app might be for a specific device but if it recognized the IMEI on my phone then it should be able to change it.