Does anybody still run CM Recovery 1.3.1? - G1 Android Development

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)

Related

Signing the update.zip in Mac OS X?

I'm sure this has been asked before but after prolific searching of the forums and our friend Google I turn to you guys for help. As the title says I'm using OS X and I need a solution (that isn't dual booting to use XP) to signing the update.zip so that I can customise aspects of my ROM, I'm very eager to learn how to do this and this so far seems to be quite an annoying problem.
Thanks for your time in advance
tristyB said:
I'm sure this has been asked before but after prolific searching of the forums and our friend Google I turn to you guys for help. As the title says I'm using OS X and I need a solution (that isn't dual booting to use XP) to signing the update.zip so that I can customise aspects of my ROM, I'm very eager to learn how to do this and this so far seems to be quite an annoying problem.
Thanks for your time in advance
Click to expand...
Click to collapse
pm me............
korndub said:
pm me............
Click to expand...
Click to collapse
Hi korndub,
Cannot you post the answer here so everybody that uses OS X can also sign?
I'm also having problems signing full roms (update.zip files) with signapk.jar
Any help is appreciated
rommelin said:
Hi korndub,
Cannot you post the answer here so everybody that uses OS X can also sign?
I'm also having problems signing full roms (update.zip files) with signapk.jar
Any help is appreciated
Click to expand...
Click to collapse
i have a folder on the desktop which contains the signapk.jar and both sets of keys...put the Archive.zip that you have created and want to sign in this folder, then open terminal
in terminal, you type
$cd FOLDER-containing-files
$java -jar signapk.jar testkeys.x509.pem testkey.pk8 Inputfile.zip outputfile.zip
the outputfile.zip is your update which is signed....
OK, I do all that I think.
Heres my process.
Download ROM
Extract downloaded zip to folder eg update
Make changes to files
Compress folder back to zip eg update1.zip
java -jar signapk.jar testkeys.x509.pem testkey.pk8 update1.zip update_signed.zip
rename and copy the signed file to sd
reboot recovery
wipe and apply update
It doesn't moan about the signing (so I assume its ok) but I get an update script not found error and it doesn't install.
I haven't changed the update scripts, only the boot.img and one or two scripts in system.
Does every file I change have to be resigned as well? I muct be missing something here
on OSX 10.5
Signing has nothing to do with that error. Make sure that the update-script is in the correct path.
META-INF/com/google/android/update-script
it is, is a normal update.zip (ie cyanogen rom), and the only file I've changed is boot.img and a2sd in system/bin
i have a folder on the desktop which contains the signapk.jar and both sets of keys...put the Archive.zip that you have created and want to sign in this folder, then open terminal
in terminal, you type
$cd FOLDER-containing-files
$java -jar signapk.jar testkeys.x509.pem testkey.pk8 Inputfile.zip outputfile.zip
the outputfile.zip is your update which is signed....
Click to expand...
Click to collapse
Thank you so much, this works for me, I might try and build it into an automator workflow
Edit: I spoke too soon, I get the update script error also
Edit Again: my update-script is in the same place as it should be also
Wonder if this is a specific OSX problem? We do have apples 'interpretation' of java don't we?
dazcox5181 said:
Wonder if this is a specific OSX problem? We do have apples 'interpretation' of java don't we?
Click to expand...
Click to collapse
haha, yeah that's right, those crazy cats at Apple. but I assume that korndub also has Apples 'interptretation' so something else could be the problem also
perhaps the way we zip the archive?
dazcox5181 said:
perhaps the way we zip the archive?
Click to expand...
Click to collapse
sadly not, I just used a application that zips in a PC format (without mac hidden files) and no joy. Good idea though.
Edit: Just tried archiving the zip but not compressing. Thought I was on to something. I wasn't.
Another update, I have tried the same in Fedora 11 and again, getting the update script error message when I flash.
I signed modified update for 3 different builds on my Mac, everything worked w/o problems every time. I did everything like described in readme and several times here. So, it's not a global OS X problem.
BTW, I used muCommander to directly modify all zips.
neuro159 said:
I signed modified update for 3 different builds on my Mac, everything worked w/o problems every time. I did everything like described in readme and several times here. So, it's not a global OS X problem.
BTW, I used muCommander to directly modify all zips.
Click to expand...
Click to collapse
When I find the time later on I will give the muCommander a go. Fingers crossed.
dazcox5181 said:
OK, I do all that I think.
Heres my process.
Download ROM
Extract downloaded zip to folder eg update
Make changes to files
Compress folder back to zip eg update1.zip
java -jar signapk.jar testkeys.x509.pem testkey.pk8 update1.zip update_signed.zip
rename and copy the signed file to sd
reboot recovery
wipe and apply update
It doesn't moan about the signing (so I assume its ok) but I get an update script not found error and it doesn't install.
I haven't changed the update scripts, only the boot.img and one or two scripts in system.
Does every file I change have to be resigned as well? I muct be missing something here
on OSX 10.5
Click to expand...
Click to collapse
you dont archive (zip) the folder, this is where you are having the issue... say you extracted the rom to ROMFOLDER, what you need to do is go into that folder, select all, then right click or two finger click and choose Compress - you will end up with an archive that contains all sub folders, if you zip the folder then you have a folder within a folder and that is where all goes south..
korndub said:
you dont archive (zip) the folder, this is where you are having the issue... say you extracted the rom to ROMFOLDER, what you need to do is go into that folder, select all, then right click or two finger click and choose Compress - you will end up with an archive that contains all sub folders, if you zip the folder then you have a folder within a folder and that is where all goes south..
Click to expand...
Click to collapse
Oh my god, you're right. And I think I actually read that somewhere before now you've reminded me. Damn. Thanks though! Thanks a lot!
Awesome, knew it was me being stupid.
sure thing guys! glad i could help...
Always something stupid...

Need Beta testers for a Mac SBF Flasher

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 just broke webtop

Can someone who has webtop tar up thier osh and post a place I can grab it.
I have been working to get a full version of ubuntu going in webtop, and I was working on reverse engineering the way they did it with the bionic and that did not work well
I will buy a beer or coffee for anyone who can do this for me.
Thanks,
Jim
just got home. give me a few minutes
what file format you want?
You rock, does not matter much, a tar or zip or 7zip or bz2... whatever you put it in I can take it and put it back in place from there.
Thanks,
Jim
lol. while it was pulling, i was messing around with my phone and crashed it..
re-pulling
OSH.IMG.TGZ
dd if=/dev/block/webtop of=/mnt/sdcard/osh.img
did you get it?
Yes, I did. I also gave a donation to you.
THANK YOU!
Jim
I was able to get my webtop working again, by whacking tomoyo, that is the Linux FACL that they are using for webtop.
Thanks again for your help.
Jim
I just broke webtop and I was hoping you could explain to me how to restore it using this .img.tar.gz file. I don't have a clue what to do with it. Please help! I messed up my osh file pretty miserably.
matthewsteross said:
I just broke webtop and I was hoping you could explain to me how to restore it using this .img.tar.gz file. I don't have a clue what to do with it. Please help! I messed up my osh file pretty miserably.
Click to expand...
Click to collapse
it think it's a dd image, so just do the reverse;
dd if=osh.img of=/dev/block/webtop
I'm sorry. I'm oblivious as to what you're talking about... I'm am sorry for my ignorance, is that a command prompt thing for windows or is that something I would use adb for? Also, how do I thank you for replying?
matthewsteross said:
I'm sorry. I'm oblivious as to what you're talking about... I'm am sorry for my ignorance, is that a command prompt thing for windows or is that something I would use adb for? Also, how do I thank you for replying?
Click to expand...
Click to collapse
This thread was from before we had the FXZ files to flash from fastboot.
I believe the proper way to restore webtop would be to grab the 55.11.16 release FXZ. Extract it and extract moto-fastboot to the same directory. Run a cmd and cd to the directory.
Put your phone into fastboot mode by holding volume down while you power it on, hook it up via usb, and
(or you can use the two button salute and choose it from the boot menu)
Code:
moto-fastboot.exe flash webtop grfs.img
You can then use motorola's faux-55.13.26 update to reapply the patches to update the webtop partition to the 55.13.25 version.
This tar.gz file would still work, you'd need to decompress it, adb shell into the phone, run su (to get root) and then run the commands from the directory where the img is stored. I don't think you need busybox to run dd... could be wrong
Flashing with fastboot is the more elegant solution.
(note it's probably not a good idea to write the img files from the fxz directly with dd.)DON'T CROSS THE STREAMS!
I got it to work by flashing in fastboot, thanks for all your help! All is well again and I even have Linux unlocked and running the XFCE-4 desktop environment. Thanks for all your help!

[Q] How to install Jhinta Kernel ?

Somebody could please tell me the right way to install the Jhinta Kernel on a Dualboot tablet ?
Well, i know I have to dowload these files and replace it in the OLiFE folder.
but how about the rest of the files ? (the initrd folder and 3.1.10-g8c2655b-dirty.tar.gz)
Thanks and advance my friends
when you using linux the best way is to biuld it by yourself, you can do that on tablet itself.
i'll rite you an script which do it by itself okay?
NoDiskNoFun said:
when you using linux the best way is to biuld it by yourself, you can do that on tablet itself.
i'll rite you an script which do it by itself okay?
Click to expand...
Click to collapse
That would be amazing man, I've never been able to compile jhintas kernel I always get errors (its hard debugging the problem when you have no idea about the commands your using lol)
JoinTheRealms said:
That would be amazing man, I've never been able to compile jhintas kernel I always get errors (its hard debugging the problem when you have no idea about the commands your using lol)
Click to expand...
Click to collapse
kernel.tar.gz
extract it in home directory and run ./kernel-updater.sh from terminal ... needs about an hour so plug in AC
Trying this.
You're awesome man !
FLAWLESS !!! After all the script, all i need to do was flash the kernel files by way of OLiFE.
prog19 said:
Trying this.
You're awesome man !
FLAWLESS !!! After all the script, all i need to do was flash the kernel files by way of OLiFE.
Click to expand...
Click to collapse
normally the script should flash it by itself ...
this one should flash it ... make an mistake in last one
NoDiskNoFun said:
normally the script should flash it by itself ...
this one should flash it ... make an mistake in last one
Click to expand...
Click to collapse
So just to make sure im doing this right, Ive deleted tf101-gnu-kernel from the previous script and ran the new version (Here comes the really noob question) how do i know if jhintas kernel has been installed, would uname -a work?
JoinTheRealms said:
So just to make sure im doing this right, Ive deleted tf101-gnu-kernel from the previous script and ran the new version (Here comes the really noob question) how do i know if jhintas kernel has been installed, would uname -a work?
Click to expand...
Click to collapse
you can see it in systemonitor ...
uname -r should give you 3.1.10-(blah)-dirty ... the you have jhinta's kernel on it ...
Hey man Ive ran the script 3 times and im still on 2.6, I get:
"Cloning into 'abootimg'...
fatal: unable to connect to gitorious.org:
gitorious.org[0: 42.2.0.192]: errno=Connection timed out
gitorious.org[1: 2a02:c0:1014::1]: errno=Network is unreachable
/home/josh/kernel-updater.sh: 11: cd: can't cd to abootimg
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat `abootimg': No such file or directory
chmod: cannot access `/usr/bin/abootimg': No such file or directory"
This is the error i get when ive tried manually.
Hi,
I've been trying out NoDiskNoFun's net-install ubuntu as well as this script but i've been getting this message on the terminal:
INFO: task kinteractiveup:61 blocked for more than 120 seconds
Can anyone point me in the right direction on how to fix this?
I have been able to get to the point where only trackpad is not working, but after a few minutes while using it the window manager crashes and the only thing i can do is open a new terminal (via Ctrl+Search+TrackpadToggle). I'm wondering if the problem i mention above is the cause.
jammerkiai said:
Hi,
I've been trying out NoDiskNoFun's net-install ubuntu as well as this script but i've been getting this message on the terminal:
INFO: task kinteractiveup:61 blocked for more than 120 seconds
Can anyone point me in the right direction on how to fix this?
I have been able to get to the point where only trackpad is not working, but after a few minutes while using it the window manager crashes and the only thing i can do is open a new terminal (via Ctrl+Search+TrackpadToggle). I'm wondering if the problem i mention above is the cause.
Click to expand...
Click to collapse
first: wrong thread! post this in Net-Install thread please
this:INFO: task kinteractiveup:61 blocked for more than 120 seconds means nothing and does nothing, just ignore it. i don't know where it comes
i need more details, i don't know hich windows manager you mean. please post used version and your configfuration: Display Manager, Desktop Environment, etc
AND post this in right thread please
---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------
JoinTheRealms said:
Hey man Ive ran the script 3 times and im still on 2.6, I get:
"Cloning into 'abootimg'...
fatal: unable to connect to gitorious.org:
gitorious.org[0: 42.2.0.192]: errno=Connection timed out
gitorious.org[1: 2a02:c0:1014::1]: errno=Network is unreachable
/home/josh/kernel-updater.sh: 11: cd: can't cd to abootimg
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat `abootimg': No such file or directory
chmod: cannot access `/usr/bin/abootimg': No such file or directory"
This is the error i get when ive tried manually.
Click to expand...
Click to collapse
try to run script while you have internet connection
I did have an internet connection because i downloaded the script before hand lol, Even when i tried compile it manually on my Ubuntu desktop i got the same error, I'm so confused lol
JoinTheRealms said:
I did have an internet connection because i downloaded the script before hand lol, Even when i tried compile it manually on my Ubuntu desktop i got the same error, I'm so confused lol
Click to expand...
Click to collapse
may you can't connect to github cause of your proxy settings like you can't in china ... try ping github.org
I have tried running the script manually. Everything goes smooth until i get to where i am supposed to copy the zImage from /TF101-GNU-kernel...
The zImage is not in that folder.
Rinkydink said:
I have tried running the script manually. Everything goes smooth until i get to where i am supposed to copy the zImage from /TF101-GNU-kernel...
The zImage is not in that folder.
Click to expand...
Click to collapse
It is in ./TF101-GNU-Kernel/arch/arm/boot/ if the build process was succesfull
Rinkydink said:
I have tried running the script manually. Everything goes smooth until i get to where i am supposed to copy the zImage from /TF101-GNU-kernel...
The zImage is not in that folder.
Click to expand...
Click to collapse
it isn`t build right ...
So i have been following these posts for the past week trying to find out how to get jhintas kernel to work with my tab. Finally i got it through compiling, after fixing a couple bugs, but now i am not sure what to do. I have used OLife and i am running dual boot. I've tried making the flashable image using the dualboot.cfg found in OLIfe and i have tried a couple different initrd found on xda but nothing works. After flashing the proper partition, found by dissecting lilstevie's update script, the system now crashes during boot. It complains about read-only filesystem. This is very frustrating and would greatly appreciate assistance.
nazbert said:
So i have been following these posts for the past week trying to find out how to get jhintas kernel to work with my tab. Finally i got it through compiling, after fixing a couple bugs, but now i am not sure what to do. I have used OLife and i am running dual boot. I've tried making the flashable image using the dualboot.cfg found in OLIfe and i have tried a couple different initrd found on xda but nothing works. After flashing the proper partition, found by dissecting lilstevie's update script, the system now crashes during boot. It complains about read-only filesystem. This is very frustrating and would greatly appreciate assistance.
Click to expand...
Click to collapse
you don't need dualboot.cfg ... you need bootimg.cfg
NoDiskNoFun said:
you don't need dualboot.cfg ... you need bootimg.cfg
Click to expand...
Click to collapse
I am having the very same problem. I managed to compile the kernel and now i have my zImage and I have been trying to use different initramfs. After editing dualboot.cfg i managed to get rid of the read only problem by changing ro to rw. Now it boots but freezes at boot. Sometimes it gets as far as to a black screen with the cursor but then it just freezes again. I am a total noob and i dont know if i need a different initramfs or if i need to configure something else.
I am using second boot partition for Ubuntu.
My dualboot.cfg now looks like this
bootsize = 0x8d6000
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline = [email protected] [email protected] vmalloc=128M gpt video=tegrafb console=tty0 usbcore.oldscheme_first=1 [email protected] root=/dev/mmcblk0p8 rw quiet splash
If anyone would be able to help me i would be very glad since I am litteraly going insane over this.

DEBRICK IMAGES - Hardbrick recovery plan

With all the random qhsusb_bulk hardbricks coming around, I've decided to create a thread to share debrick.img files just in case. You do not need to create this, but if you ever need it, you'll be glad you did.
EXPLANATION:
If you ever HARDBRICK your phone, which can be caused by flashing an incompatible ROM, bad bootloader flash, or anything, your processor will fallback into a mode called USB_BULK mode. In this mode, it will await an SD card with a special image flashed to it, called debrick.img, and boot to that. Once booted from the SDcard, it will await a firmware flash from a computer (download mode.)
However, this image needs to be specific to the bootloader version the phone was running before the hardbrick occured. That's why I've created this thread: people on different bootloaders can share their debrick images.
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
HOW TO USE ONE:
If you ever have the unfortunate luck of needing to use a debrick image, here's what to do:
-Download Win32DiskImager
-Put your microsd into your PC (yes you will need an adapter in some cases)
-Use Win32DiskImager to write the debrick.img to the SD card
-Take battery out of phone
-Put the SDcard into the phone and put the battery back in
-Do Vol Dn+Power+Home
-Your device should boot into Download Mode, and you should see "SDCARD MODE" at the top right
-Flash stock firmware using Odin
Downloads will be added to the 2nd post
Downloads
PB1 BOOTLOADER DEBRICK
PD1 BOOTLOADER DEBRICK (thanks @klabit87)
PLEASE SHARE YOUR OWN DEBRICK IMAGES! I WILL ADD THEM HERE
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
al50 said:
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
Click to expand...
Click to collapse
It is completely based on bootloader version. You can use "Phone Info - Samsung" to confirm before creating an image.
This is great would be nice if you could create Bod5 img for us who are still able to downgrade
Sent from my SM-G900V using Tapatalk
When I get a chance I'll make one for the OC4. Just want to be sure to do it correctly. Since I'm on UL OC4 Bootloader, PB1 firmware
Nandr0idC0nsumer said:
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card
Click to expand...
Click to collapse
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
ben_pr said:
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
Click to expand...
Click to collapse
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
[email protected] said:
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
200mb is all thats needed on sd.
Only for samsung devices.
Nandr0idC0nsumer said:
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
Click to expand...
Click to collapse
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
ben_pr said:
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
Click to expand...
Click to collapse
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Nandr0idC0nsumer said:
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Click to expand...
Click to collapse
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
Nandr0idC0nsumer said:
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
Click to expand...
Click to collapse
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
ben_pr said:
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
Click to expand...
Click to collapse
Good point. I will update the OP later. This is not my package btw
Nandr0idC0nsumer said:
Good point. I will update the OP later. This is not my package btw
Click to expand...
Click to collapse
My mistake; I thought you made the zip!
Nandr0idC0nsumer said:
200mb is all thats needed on sd.
Only for samsung devices.
Click to expand...
Click to collapse
Thanks
Sent from my SM-G900V using XDA-Developers mobile app
ben_pr said:
My mistake; I thought you made the zip!
Click to expand...
Click to collapse
Lol nope. Usually I like to have it all in the updater-script so I wouldn't have had a seperate script
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
akaplo said:
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
Click to expand...
Click to collapse
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Nandr0idC0nsumer said:
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Click to expand...
Click to collapse
See my thread. http://forum.xda-developers.com/showpost.php?p=67159556&postcount=14

Categories

Resources