Related
If you do, can you please do me a favor: Can you please copy the gzip executable to /sdcard and upload to this thread?
Boot into recovery and:
Code:
mount /sdcard
cp /sbin/gzip /sdcard/gzip
devsk said:
If you do, can you please do me a favor: Can you please copy the gzip executable to /sdcard and upload to this thread?
Boot into recovery and:
Code:
mount /sdcard
cp /sbin/gzip /sdcard/gzip
Click to expand...
Click to collapse
ignore sig. reflashed 1.3.1. when i cp /sbin/gzip /sdcard/gzip i get cannont stat /sbin/gzip no such file or directory
edit: i found gzip in /system/bin. just take off .txt extension.
Thanks for you efforts. But the problem is I need the static binary that was present in the 1.3.1. The one in /system/bin is a dynamic one and won't run (tried it already) in 1.4 recovery.
I need to figure out where did that static binary in 1.3.1 come from. That binary is 3 times faster in compressing than the one in busybox.
sorry i couldn't find it. did you try asking cyanogen?
david1171 said:
sorry i couldn't find it. did you try asking cyanogen?
Click to expand...
Click to collapse
He is on vacay until the weekend is over.
erissiva said:
He is on vacay until the weekend is over.
Click to expand...
Click to collapse
can you extract it from the update.zip?
i believe the link was
http://n0rp.chemlab.org/android/cm-recovery-1.3.1-signed.zip
edit: nvm its proly a .img inside. i believe theres an image unpacking tool out here, ill try and find it
B-man007 said:
can you extract it from the update.zip?
i believe the link was
http://n0rp.chemlab.org/android/cm-recovery-1.3.1-signed.zip
edit: nvm its proly a .img inside. i believe theres an image unpacking tool out here, ill try and find it
Click to expand...
Click to collapse
Thanks guys, you are awesome!
Hmm... [No Luck]
Devsk, I just scowered every recovery image that Cyanogen has released (using unpack.pl http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images) for the gzip file you mentioned, however, I saw no static-binary that you speak of.
(yes, I checked every image file, including the ones in the .zip update file that cyanogen released for 1.3.1)
I'm actually curious myself, and have begun searching JF's recovery images too... still no luck...
HOWEVER, and I'm not too keen on scowering... perhaps if you ask Cyanogen if he ever released a recovery image in one of his update.zip's... perhaps thats what you're looking for?! *ponders*
good luck! I think i'm going to check it out!
rikupw said:
Devsk, I just scowered every recovery image that Cyanogen has released (using unpack.pl http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images) for the gzip file you mentioned, however, I saw no static-binary that you speak of.
(yes, I checked every image file, including the ones in the .zip update file that cyanogen released for 1.3.1)
I'm actually curious myself, and have begun searching JF's recovery images too... still no luck...
HOWEVER, and I'm not too keen on scowering... perhaps if you ask Cyanogen if he ever released a recovery image in one of his update.zip's... perhaps thats what you're looking for?! *ponders*
good luck! I think i'm going to check it out!
Click to expand...
Click to collapse
when in recovery 1.3.1, what does 'which gzip' give you? I am not sure where that executable is being gotten but doing 'gzip -h' and 'busybox gzip -h' resulted in two different things in 1.3.1 but same in 1.4.
One question: is it safe to go back to 1.3.1 and switch back & forth? I need to figure where some of the executables are coming from and how come it can load the same dynamic executable in 1.3.1 but not in 1.4.
devsk said:
when in recovery 1.3.1, what does 'which gzip' give you? I am not sure where that executable is being gotten but doing 'gzip -h' and 'busybox gzip -h' resulted in two different things in 1.3.1 but same in 1.4.
One question: is it safe to go back to 1.3.1 and switch back & forth? I need to figure where some of the executables are coming from and how come it can load the same dynamic executable in 1.3.1 but not in 1.4.
Click to expand...
Click to collapse
yes, it is safe, the ONLY issue i've had is I cannot seem to be able to successfully edit a recovery.img and reflash it, it works, the only issue is I don' thave command I get the "A N D R O I D" when i try to use terminal at the recovery menu, (although everything works via adb)
I am on 1.4, I just downloaded ALL the Cyanogen.zips (I hope I don't overuse his bandwidth, I would feel so bad...) but I found no recovery images within his .zips,
try flashing a 1.3.1, (I'm not able to use my android phone, as I left it at work haha)
and trying which. just m ake sure you do a nandroid backup before you flash back to 1.3.1 (though I doubt it should make a difference)
Code:
IDEA!
try to mount all your partitions within the recovery command (from the phone, not adb).
type
# mount -a
(it'll error, don't worry its normal )
# exit
press enter, and then type "which gzip"
I think that its actually loading the /system/bin/gzip... which would make sense... but idk, can you give it a try?
*EDIT AGAIN*
ok, the reason for what I told you, is that I noticed that if you reset the terminal (exit, enter) its like re-adding the PATH to the shell, i guess? I'm still a wee bit new to linux, but I know how to search (or rather... scower)
With the help of red_menace over at the apple support forum, I present Mac users with an application that will sign their .apk and .zip files.
It is a droplet application, meaning you just have to drag the file you want signed onto the application itself. A new file will be created with -signed at the end of the file name.
For this to work you need to have testsign.jar in your root directory. The root directory is the first place you come to when you click on the mac hard drive.
If anyone wants to use or edit the script that's fine with me, I really didn't do much, just asked the right people for help.
Android-sign.zip Download
Android-sign.zip has both the testsign.jar and android-sign application.
EDIT: Sorry about the mixup. Testsign.jar is now linked above.
thank you sir! will try tonight
Exception in thread "main"
java.lang.NoClassDefFoundError: testsign
I cant find the testsign.jar its not in the tool directory of my SDK that I downloaded from Androids website
Where can I get this testsign.jar?
*EDIT*
I found the testsign.jar in the forums. You can get it here: http://forum.xda-developers.com/showthread.php?t=538020
But I still get the same error I've placed the program and the testsign.jar file in the same directory.
I have some cool skins in the making! I just need to know how to sign these files! I'm on a mac.
Why am I getting the error?
wow i need this bad...now lets c if i know how to get it 2 work....
MurderDeathKill said:
But I still get the same error I've placed the program and the testsign.jar file in the same directory.
I have some cool skins in the making! I just need to know how to sign these files! I'm on a mac.
Why am I getting the error?
Click to expand...
Click to collapse
are you putting the testsign.jar in your ROOT dir? aka where adb is
same error
Okay, so I'm getting the same error. And yes, my testsign.jar/Android-sign.app are both in my sdk/tools dir.
Not sure what the problem is.
Hope I can get this to work
jaaronmoody said:
are you putting the testsign.jar in your ROOT dir? aka where adb is
Click to expand...
Click to collapse
What file is the adb? I understand what adb means and what it does, but I don't know how to identify it.
Ok so since im new to this can someone can make a really dumb guide for me from dowloading the app to putting the test.jar file please.
im getting the same error, this is a huge step though when u figure out whats going on with the rest of our Auto-sign, repost thanks nd thumbs up
nice...thx for sharing this. will come in handy
oops, still getting used to all this. haha
ffff00 said:
Okay, so I'm getting the same error. And yes, my testsign.jar/Android-sign.app are both in my sdk/tools dir.
Not sure what the problem is.
Hope I can get this to work
Click to expand...
Click to collapse
the testsign.jar needs to be in the root directory of your computer. The app can be placed anywhere you would like. Where ever you put the app, the new signed file will be also.
guys so lets say i put meltus audio hack in cyanogen 4.9999 and i want to sign the whole build back up how would i do that.
thank you
jessetbenton said:
the testsign.jar needs to be in the root directory of your computer. The app can be placed anywhere you would like. Where ever you put the app, the new signed file will be also.
Click to expand...
Click to collapse
Oh okay, thanks.
You said to put it in the same folder as adb is why I was confused.
I'll try this out in a few.
ffff00 said:
Oh okay, thanks.
You said to put it in the same folder as adb is why I was confused.
I'll try this out in a few.
Click to expand...
Click to collapse
no i said that, and it is where adb is.... at least for me... in the root dir, if you move the adb file there you don't have to enter the path every time you enter adb commands in the terminal
ffff00 said:
Oh okay, thanks.
You said to put it in the same folder as adb is why I was confused.
I'll try this out in a few.
Click to expand...
Click to collapse
i think what jaaronmoody was talking about is just putting your adb file into the root directory instead of adding to the bin. but im pretty new to the whole terminal and coding stuff, so i just know what i've picked up since having my g1.
guys does anybody know about signing folders again to make them flashable?
G1_Lucky said:
guys so lets say i put meltus audio hack in cyanogen 4.9999 and i want to sign the whole build back up how would i do that.
thank you
Click to expand...
Click to collapse
well if the file is good. you just have to drag the cm 4.9999.zip file onto the app and it will spit out the new signed version.
What I think is more complicated is actually modifying those files. I use virtualbox to run windows and do everything with 7zip.
Anyone know of a zip program similar to 7zip to edit the apk and zip files?
Dude! Thanks! Alright guys get ready now that I have everything in place ADB, and signing my .zip files expect Luck's turn at android development lol. Im hecka grateful for everybody but now im ready haha thanks guys
Thanks for the help.
Works like a charm.
Awesome droplet.
Hi, guys. I am a new member here at XDA and would like some people to test a version of Darkonion's Dosbf script modified for Macs. I have tested this this with my Mac, and a Droid X, and everything has gone wonderfully. I need to verify that it actually works with other Macs, so if anyone would like to help me out here, I would be very grateful.
Remember to wipe data/cache after SBF to be safe.
If you've gotten the message "error: no sbf_flash program" then you'll need to restart terminal and run the command "./sbf_flash droid2.sbf" after you cd to the SBF_Flasher_1.4 directory.
Update: SBF_Flasher_1.4
MAJOR UPDATE: Using the right sbf_flash finally. If for some reason this zip doesn't work, go here:
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
If anyone needs support, PM me and I can help.
stuck trying to flash
I keep getting this message when in terminal
Press any number or letter key, then enter to continue.
l
Error: No sbf_flash program
Exiting
bigoz71 said:
I keep getting this message when in terminal
Press any number or letter key, then enter to continue.
l
Error: No sbf_flash program
Exiting
Click to expand...
Click to collapse
If that happens, it basically means that the sbf_flash file is not an executable. Try this.
In terminal, type "chmod +x" and leave a space, then open the SBF_Flasher_1.3 folder and drag sbf_flash into terminal. Here's how it should look.
chmod +x /location of folder/SBF_Flasher_1.3/sbf_flash"
you don't have to put the SBF file on your sdcard, you just copy it to the SBF_Flasher folder on your computer and rename it droid2.sbf
i get to the point when it says "Press any number or letter key, then enter to continue" when i press a number or letter it gives me an error saying "Error: No sbf_flash program" any insight on what i may be doing wrong?
Edit:
tried the above instructions, and still not working. my phone has been stuck in bootload all day :-(
RockTheRed52 said:
i get to the point when it says "Press any number or letter key, then enter to continue" when i press a number or letter it gives me an error saying "Error: No sbf_flash program" any insight on what i may be doing wrong?
Edit:
tried the above instructions, and still not working. my phone has been stuck in bootload all day :-(
Click to expand...
Click to collapse
Make sure you pull the battery in between trying, otherwise you'll have to find another battery.
What phone and software version are you running? Did you get the correct SBF file?
G7man said:
Make sure you pull the battery in between trying, otherwise you'll have to find another battery.
What phone and software version are you running? Did you get the correct SBF file?
Click to expand...
Click to collapse
im using a D2 with the gingerbread leak, i was installing apex2.0 however me being careless downloaded the DX version by accident. then all hell broke lose lol.
im pretty sure i downloaded the correct SBF file. however if you have you prefer i would like to know
double post. my fault.
RockTheRed52 said:
im using a D2 with the gingerbread leak, i was installing apex2.0 however me being careless downloaded the DX version by accident. then all hell broke lose lol.
im pretty sure i downloaded the correct SBF file. however if you have you prefer i would like to know
Click to expand...
Click to collapse
Well, I don't own a D2, so here is all I can say.
1. Make sure you chmod +x both the sbf_flash and the SBF_Flasher.sh files
2. Download the 2.3.20 SBF, or whatever the most current one is and copy it to the SBF_Flasher folder. Rename the sbf "droid2.sbf" case-sensetive and without quotes
3. Run SBF_Flasher.sh and tell me at what point it errors, and what it says.
G7man said:
Well, I don't own a D2, so here is all I can say.
1. Make sure you chmod +x both the sbf_flash and the SBF_Flasher.sh files
2. Download the 2.3.20 SBF, or whatever the most current one is and copy it to the SBF_Flasher folder. Rename the sbf "droid2.sbf" case-sensetive and without quotes
3. Run SBF_Flasher.sh and tell me at what point it errors, and what it says.
Click to expand...
Click to collapse
this is where i am getting stuck at
Press any number or letter key, then enter to continue.
chmod +x /Users/alkap16/Desktop/SBF_Flasher_1.3/sbf_flash 1
Error: No sbf_flash program
Exiting
although i am not sure if i am "chmod +x" the SBF_Flasher.sh file correctly.
sorry for all this this is my first time doing anything like this on my phone or computer.
RockTheRed52 said:
this is where i am getting stuck at
Press any number or letter key, then enter to continue.
chmod +x /Users/alkap16/Desktop/SBF_Flasher_1.3/sbf_flash 1
Error: No sbf_flash program
Exiting
although i am not sure if i am "chmod +x" the SBF_Flasher.sh file correctly.
sorry for all this this is my first time doing anything like this on my phone or computer.
Click to expand...
Click to collapse
Ok, you need to chmod both files before running the SBF_Flasher.sh file. Also, it should look like "chmod +x /users/alkap16/Desktop/SBF_Flasher_1.3/sbf_flash". make sure the file name is sbf_flash, not sbf_flash 1.
Sent from my DROIDX using XDA App
finally got everything to work. but when the sbf is done flasing im still stuck in the bootloader with no no way of getting into recovery mode.
RockTheRed52 said:
finally got everything to work. but when the sbf is done flasing im still stuck in the bootloader with no no way of getting into recovery mode.
Click to expand...
Click to collapse
Well, if it hasn't worked, and you don't have a windows pc, you should definitely try 1KDS's live disk, or this link.
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html
I've been trying it, and I'm getting the same error for no sbf_flash program. I've tried chmod +x on both sbf_flash and SBF_FLASHER.sh
any ideas?
The other one you posted last is still a no go, as my mac can't burn disks.
craig_s said:
I've been trying it, and I'm getting the same error for no sbf_flash program. I've tried chmod +x on both sbf_flash and SBF_FLASHER.sh
any ideas?
The other one you posted last is still a no go, as my mac can't burn disks.
Click to expand...
Click to collapse
You should definitely download sbf_flash from blog.opticaldelusion.org and see if that works. It's probably an issue with you not doing "chmod +x" right. I would try typing "chmod +x" leaving a space, and dragging sbf_flash into terminal. If all else fails, get your hands on a Windows machine, or use a VM, but I've never had success with VM's. Let me know what happens.
-G7man
Giving it a second go (I had my brother fix it last time, he doesn't want to do it this time). Should I replace sbf_flash that I downloaded with the old one?
Edit: still doesn't work!!! You wouldn't happen to know how to put 1kdStaz's liveboot onto an external hdd, or how to partition my hdd to boot off of that?
craig_s said:
Giving it a second go (I had my brother fix it last time, he doesn't want to do it this time). Should I replace sbf_flash that I downloaded with the old one?
Edit: still doesn't work!!! You wouldn't happen to know how to put 1kdStaz's liveboot onto an external hdd, or how to partition my hdd to boot off of that?
Click to expand...
Click to collapse
I know you can boot off of a usb drive, but I'm not the person to talk to for that kind of thing. I'd recommend talking to 1KDS, he's really nice.
- G7man
Try chmod 777 on the sbf_flash file, that worked for me...
Although, I have another question, does the sbf_flash file require an Intel based system? I'm using a PowerMac G5 with PPC processors and I get
./sbf_flash: line 3: /tmp/sbf_flash_754_746/Darwin: Bad CPU type in executable
Click to expand...
Click to collapse
I downloaded the Android SDK on the website and the drivers from MotoDev and placed them on my desktop. I ran the drivers and they installed fine. I unzipped the SDK, created a new folder in my C: drive called AndroidSDK and placed the unzipped folder in that folder.
I opened Command Prompt and entered:
cd C:\AndroidSDK\android-sdk-windows\tools
then entered:
fastboot oem unlock
and got this error:
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this issue.
I then went into the SDK and read the readme where it says that adb was moved. It says it was moved to platforms. When I open the folder there is nothing in there.
try the path that ends with "platform-tools" instead
Sent from my Xoom using XDA Premium App
Ok I figured it out. I clicked on something and it brought up a repo. I download the missing platform-tools.
I ran the commands again and I'm still getting the errors. Should I copy everything from platform-tools into the tools directory?
gqstatus0685 said:
I tried that also. I forgot to add that in my first post. There is nothing inside that folder. Am I missing adb? Is there a way to download it and drop it into that folder? I'm lost on this.
Thanks.
Click to expand...
Click to collapse
Did you open the SDK Manager and make sure all your packages are updated?
gnackattack said:
Did you open the SDK Manager and make sure all your packages are updated?
Click to expand...
Click to collapse
I did do that but cancelled after it installed the platform-tools. Should I let it download everything? It looked like it was going to take a long ass time.
**** I ended up downloading all the updates for 3.1 and entered the commands again. This time it was able to cd into the platform-tools but I can't enter the command fastboot oem unlock because I get error:
"fastboot" is not recognized as an internal or external command, operable program or batch file
Just my luck...
fastboot is in the "tools" folder, not the "platform-tools" folder.
gnackattack said:
fastboot is in the "tools" folder, not the "platform-tools" folder.
Click to expand...
Click to collapse
Ok I changed CD but now it's telling me it can't find a file that's located in platform-tools. Should I copy all the files from platform-tools and move them into the tools folder?
*********************************************************
Ok. I moved the file and it worked. My Xoom is unlocking. I have the worst luck when I borrow someone else's laptop.
Copy any files it tells you it can't find. I haven't encountered that issue myself, but that's the solution I've seen others recommend.
I'd like to thank Gnac and the other people who helped me achieve root with the issues I was having.
Anyway I have an SD card in my Xoom and I don't think it's working like it should. I downloaded a file manager, loaded a .zip on there of a theme I want to install but when I boot into recovery it's not there.
I've verified it's in the SDcard with the file manager and it's in .zip format. I'd prefer to flash it instead of adb'ing it because I keep all my .zip organized in folders on my SD card. Before inserting the SD card in the Xoom I did wipe it.
I'm rooted 3.1 and I have Busybox installed. I'm running:
[email protected] #2
Any ideas how I can get the files to be seen in recovery?
Hello everyone,
I'm new here so i couldn't post on the development section and i'm forced to post this here!
So i'm following the guide for changing the CID here: http://forum.xda-developers.com/showthread.php?t=1674202
But now i'm stuck!
Ragazzi aiuto sono bloccato!
So, after editing the mmcblk0p4 file with an hex editor, i went back to the cmd and wrote this:
adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
but then i get this error: adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD cannot stat mmcblk0p4MOD : No such file or directory .
What can i do? The only thing i noticed is that when i "create" the mmcblk0p4 file i left the usb in debug mode eand charge only otherwise i couldn't run anything, then to edit mmcblk0p4 i was forced to switch the usb to hard disk. Then i switched again to "charger" mode but i get the error above and i don't know what to do.
Please help me with some suggestions! Thanks in advance!
Good thing that you couldn't post in development since this is the correct forum for this type of question
Can't stat means it can't find the source file when you try to copy it back to the sdcard. Check that you're in the correct directory when trying to do this and also I don't think you can rename the partition that way (adding "MOD")
Nevermind my comment about renaming it to MOD, I just checked the guide and I see now why it's done.
frdd said:
Good thing that you couldn't post in development since this is the correct forum for this type of question
Can't stat means it can't find the source file when you try to copy it back to the sdcard. Check that you're in the correct directory when trying to do this and also I don't think you can rename the partition that way (adding "MOD")
Click to expand...
Click to collapse
Thanks for the reply frdd, i'm just following the guide strictly! It isn't that well written and maybe that's why i'm having problems. How can i check if i'm in the right directory? I left the files in the root of the sdcard.
Here is a screenshot of what i did:
ht tp://i50.tinypic.c om/nz0wzo.png
addsfsds said:
Thanks for the reply frdd, i'm just following the guide strictly! It isn't that well written and maybe that's why i'm having problems. How can i check if i'm in the right directory? I left the files in the root of the sdcard.
Here is a screenshot of what i did:
ht tp://i50.tinypic.c om/nz0wzo.png
Click to expand...
Click to collapse
Did you really save your file in hexeditor as mmcblk0p4MOD? Maybe you forgot and the file is still named mmcblk0p4. You can check what is in your directory with the command dir in cmd.
Your phone is in Disk-drive change to Charge only when you adb push back
Mr Troop said:
Your phone is in Disk-drive change to Charge only when you adb push back
Click to expand...
Click to collapse
Thanks, but that doesn't work either already tried 3 times!
It did take me about 3 attempts keep trying
frdd said:
Did you really save your file in hexeditor as mmcblk0p4MOD? Maybe you forgot and the file is still named mmcblk0p4. You can check what is in your directory with the command dir in cmd.
Click to expand...
Click to collapse
Double checked that too! Still blocked
Follow the whole process even if (No such file or directory)is shown
Or mount as usb storage and check for the MOD file, if it's not there drag and drop the file to sdcard, then continue with the guide. Also make sure if you do this that the file is alright and not 0 in size or something.
One thought, what's up with the first time you used dd in the screenshot? What did you do to fix it? Maybe adb push can't write to the sdcard for some reason.
Mr Troop said:
Follow the whole process even if (No such file or directory)is shown
Click to expand...
Click to collapse
Hell yes!!! It worked!! Just tested the readcid command and it shows the HTC__001 one! I think the guide should be updated now!
Now i test to update the RUU
HTC__001 is Generic unbranded not superCID
SuperCID is 11111111
Mr Troop said:
HTC__001 is Generic unbranded not superCID
SuperCID is 11111111
Click to expand...
Click to collapse
You're absolutely right, sorry! I just needed the generic unbrand to get the latest RUU as wifi and radio problems were unsustainable!
The command, for some weird reasons, wasn't working but continuing as Mr Troop suggested fixed the whole thing.
Thanks for everyone who helped!!