Related
Hi guys, it just came to my mind that test-key signed update.zip files were working back in the eclair days, so i guess the problem is the new recovery in the froyo builds needing Samsung signed files. Same problem was present on the sgs when it moved to froyo, but the devs there managed to change back to old recovery to make them work again, would be nice if someone could find a similar solution for the sg3 also... for more info search for recovery 2e 3e howto in sgs dev section... i am very busy at the moment and go for vacation on Sunday so wont find time to look into this before beginning of March, but eventually someone else could do it and just needed the hint....
Ok, to give this a bump, i need someone with a eclair rom installed and a rooted system. What i need is two files: /sbin/recovery and /sbin/recovery.sh
I think if we swap those files in jpf or whatever Froyo version we could use update.zip files again...
FadeFx
I have JK1 but in sbin directory I have only recovery file, no signs of recovery.sh
sorry, my bad, recovery.sh is part of the modified clockwork mod recovery on sgs custom kernel. also i am in conversation with hardcore about this, and eventually wed have to change the file in initramfs of the kernel... but we will see. to bad i go on vacation tomorrow and will be away for 3 weeks (going to thailand, cant wait to be there...) so i wont have time to complete this, but i will gather info and eventually gsam101 could compile a zimage with old recovery...
Ok, here is my pm conversation with hardcore, seems it can be done easily with loosing new recovery, or the complicated way keeping new recovery for system calls (CSC changes and stuff) and loading old recovery when using 3 button combo. All this is done by recovery.sh
hardcore said:
No u replace /system/bin/recovery in the rom, not kernel.
For kernel if u want to reroute to another recovery u have to use some shell script logic. Check out the initramfs source of my kernel for recovery.sh.
ok, thanx... so we would have to change the file /system/bin/recovery in the zimage´s initramfs to exchange recovery, right?
can we also put the replacement recovery into /sbin to replace the original? and if how is it then called when actually entering recovery mode so we dont enter the old recovery?
thanx Gerd
The recovery executable that comes with the ROM is actually in /system/bin/recovery
Modified kernels like mine have another CWM recovery in the kernel which is in /sbin/recovery which is compiled into the kernel's read-only initramfs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Content of recovery.sh:
(lagfix stuff is about sztupys lagfix for the sgs and can be ignored for g3 at the moment.
This replaces stock froyo recovery (3e) with clockwork recovery, but same procedure applies to old 2e recovery.
Code:
#!/sbin/busybox sh
/sbin/busybox cp /sbin/fat.format /system/bin/fat.format
# use default recovery from rom if we have an update to process, so things like CSC updates work
# Use CWM if we simply entered recovery mode by hand, to be able to use it's features
if /sbin/busybox [ -f "/cache/recovery/command" ];
then
# if we use the original recovery it might modify the filesystem, so we erase our config, in order to avoid regeneration
# of the filesystems. The drawback is that the lagfix has to be re-applied by hand
/sbin/busybox rm /system/etc/lagfix.conf
/sbin/busybox rm /system/etc/lagfix.conf.old
rm /sdcard
mkdir /sdcard
#/sbin/rec2e &
/system/bin/recovery &
else
# TODO: CWM is a bit more intelligent, but it might fail to
/sbin/recovery &
fi;
Hope someone can make use of this to get update.zip working again...
Nobody looked into this yet? This would make much things easier for us...
Bump
....
realy hope we get some good progress and development on this thread....
sry but im just a noob and flashing is all i do right now
but if i can give any help feel free to ask
Gonna check this out. If I get OCD about this, v1.2 will be delayed.
This could be really useful. For everyone.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
FadeFx said:
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
Click to expand...
Click to collapse
Alright. Will do chief. Gonna bookmark this thread so I remember tomorrow.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
I have the 2.1 recovery file. . If anyone interested i think i can post if xda allows. ..
Sent from my GT-I5800 using XDA App
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
The Dark Lestat said:
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
Click to expand...
Click to collapse
Like i had to flash my phone back to make it work ^^
Did u use the sgs version of cwm or did u do an own port for the g3? I guess the sgs version wont run due to different bml layout
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
Hi Gsam101
I interested in compile custom recovery too.
Can You please share build configs for apollo projects?
just wanted to bump this thread, since i think we should now have devs that should be capable of doing such stuff, update.zip support is normally a must have for any android device
is this helpful in any way? -> http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159
No, not yet. Clockwork needs to be ported to our device to run, which i am not able to do. If u can port it i can eventually give some hints...
i have wrote to the developer of ROM Manager APP (Clockwork Recovery) asking him to support our phone. I wrote just because i saw
Don't see your phone? Email me if you want to help me get it working!
Click to expand...
Click to collapse
on his page (http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html)
i'm not good at programming so i think if the developer replies and the answer will be yes then someone like FadeFx or anyone else who can help should contact [email protected] or [email protected]
This is the "OP" or the Original Post #1....read it before asking any questions that my be answered in this post or in any of the following links!
Background: I started this thread because of the explosive growth of MikFroyo's Roms. The thread got so clogged with total new user's questions that it became difficult to find real answers to real problems. Not that new users can't learn, but I wanted to try and create a place for people who don't depend upon RomManager to control their lives!
Look, the way I see it, if you were smart enough to root your phone and start flashing new ROMs (that is the correct way to spell it btw, not roms, it is an acronym after all!), then you deserve concise answers to your issues based upon my experience in flashing phones that I have gathered in the past 3 years since I first started flashing things for my Razr phone.
I will assume you know how to use, and have properly setup, adb on your home computer. Yes, many of the commands you may see me or others post could be done through a terminal window on your phone, but your life will be much easier and more efficient if you have adb setup and working correctly on your home computer or laptop!
Here as a begining are some of the more useful posts I and others have made regarding flashing MikFroyo ROMs and some of the issues associated with this endeavor:
No touch tone recognition using MikZ?? Check solution here!
Thread that deals with changing the Power Control Widget in Notification Bar
Nick's repost of Mitchellvii's solution to Market D/L problems
Stopping your Market from Updating and losing it's skin
Nick's updated adb installation guide
joeykrim's adb getting started links
My "How to make apps2sd work" on your phone guide
The most recent repository of Netarchy Kernels
How to "flash_image" a recovery image to your phone
Pushing "Removed apps" from MikFroyo to your phone
Having "Wifi scans constantly but cannot connect" issues with MikFroyo?
Using a2sd "Sysinfo" command to learn alot about your phone's current status
Info about different Kernel types here
General statement I posted about different hardware versions
A Hardware Engineer (me ) view on "Color vs Black and White" Themes and battery useage
Much more to follow, but I thought this would get the ball rolling!
Tapatalked from my SUpersonic...
You said razr Mr. Link man
sent from Kings Ultra UNleashed
Could you post how to get adb working? I tried it a while ago but havnt given it another shot
Fr3sh2De4th said:
Could you post how to get adb working? I tried it a while ago but havnt given it another shot
Click to expand...
Click to collapse
This is not my work, but a good starting point is provided at: http://forum.xda-developers.com/showthread.php?t=694250
Browse the entire thread if you like, but the download links are in the 1st post. Thanks for the guide goes to joeykrim.
I just flashed mikfroyo, got it working, then flashed the kernal that you suggested.
My wifi turns on for a second, does not connect, then turns off and says unable to scan for wifi??? I did do a full wipe, cache and dalvik before flashing mikfroyo.
Any suggestions?
chefdrew said:
I just flashed mikfroyo, got it working, then flashed the kernal that you suggested.
My wifi turns on for a second, does not connect, then turns off and says unable to scan for wifi??? I did do a full wipe, cache and dalvik before flashing mikfroyo.
Any suggestions?
Click to expand...
Click to collapse
All in one blow flash the rom and kernel back to back. Then reboot and enjoy!
thank you I will give it a try. do I need to wipe anything before or after the flash?
Sent from my PC36100 using XDA App
chefdrew said:
thank you I will give it a try. do I need to wipe anything before or after the flash?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do the regular wipe of everything and then just flash the rom n kernel all on the same time n reboot
I just tried it and nothing has changed?
Sent from my PC36100 using XDA App
Nice thought to start this thread ! Kudos my man!
"Walk by Faith-not by Sight"
chefdrew said:
I just tried it and nothing has changed?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do u have the formatall.zip?
Not sure I know what that us, so maybe not...
Sent from my PC36100 using XDA App
chefdrew said:
Not sure I know what that us, so maybe not...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I want u to flash this zip ima link u too.
Flash the zip and then wipe everything again twice then from there flash the rom n kernel all in one recovery visit..
So
One- flash the formatall.zip
Two- wipe cache dalvik n data n sd ext two times
Three- flash rom
Four- flash kernel
On the same recovery session.
By the way what kernel u using?
Heres the formatall.zip link
http://db.tt/VKtEHjt
flash cache after format all......i don't think so...... i always boot into ROM before i do the kernel just in case, but i am paranoid haha
luckylui said:
I want u to flash this zip ima link u too.
Flash the zip and then wipe everything again twice then from there flash the rom n kernel all in one recovery visit..
So
One- flash the formatall.zip
Two- wipe cache dalvik n data n sd ext two times
Three- flash rom
Four- flash kernel
On the same recovery session.
By the way what kernel u using?
Heres the formatall.zip link
http://db.tt/VKtEHjt
Click to expand...
Click to collapse
I did a full wipe, cache/dalvik, system & boot wipe. Flashed mikfroyo then the kernal, reboot...viola!!! Everything is up & running...
Sent from my PC36100 using XDA App
chefdrew said:
I did a full wipe, cache/dalvik, system & boot wipe. Flashed mikfroyo then the kernal, reboot...viola!!! Everything is up & running...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
:-D
Good Luck buddy! Enjoy your time w the rom, its a beauty.
Installing ADB
First off I am not the originator of this guide, it can be found here and was created by nephron. I just updated it with some updated links and instructions. The newer version seemed to do a lot of the steps that were in his guide therefore I didn't need to do them to get adb to work.
Another guide I borrowed some stuff from can be found here and was created by joeykrim. If you are using a mac or linux machine go to this thread for the download links.
Again I want to give credit to those guys because they really created the original threads and I just borrowed some from both of them to create an updated install guide. This is only an install guide and if you have ADB command questions you will be better off going to those threads and asking in there or searching XDA for your answers.
Link to the Android SDK site, you might check here to see if there is an updated version of the SDK that I have link below(installer_r10)
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
7-zip - Download
Win 7 Drivers- Download-thanks shep 211
HTC Sync-The one that is in the SD card that came with your phone will work
Windows PC
USB Cable
A Rooted HTC EVO
--------------------------------------------------------------------------
Setting up the Android SDK
I installed the drivers and htc sync first, I am not sure if that matters or not.
Download the file SDK file from above and accept defaults to install it.
Once installed make sure the box is checked that says "Start SDK Manager" and hit finish.
Once SDK Manager opens click on the accept all radio button and hit install. Be patient it will take awhile.
Any problems or questions go here.
Once completed take the "android-sdk" folder and move it to the root of your hard drive (C:\).
It will be located in c:\program files(x86)\android, it's large folder so it might take a little while.
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
On the bottom half (system variables)
go to PATH and edit it to include C:\android-sdk\platform-tools
Make sure to separate it from the rest of the ones in there by a semicolon
Hit Ok
*The reason for this is so that you can run adb from any folder on your drive so that you don't have to copy your files to the tools folder. Big thanks to jadeboy and coiledwire for helping me figure this out.
--------------------------------------------------------------------------
Preparing your phone for ADB
If you are running MikFroyo it should be checked by default but you can double check it if you want.
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and it should automatically install the drivers. I've done this 4 times and every time it finds the phone just fine.
If not check out this thread here.
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands. Go here if you want to learn/test some of the basics, it's in joeykrim's thread. His push/pull of test.apk won't work because that file isn't in there. However you can just create a test.txt file on your c:\ and push/pull that to your phone. That's what I did to test that.
Easiest one to test is
Code:
adb reboot
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
Widget Text edit
Hey you might stick this in your popular solutions OP.
Link
Slow Market.
Thanks to Mitchellvii
JK you can just link to his post on this if you want since he actually found it. Here's the link
POSSIBLE SOLUTION TO SLOW MARKET:
As you use your Market, your /cache appears to fill up with .apk files call Download-1, Download-2, etc. Why Market chooses to just continually add these without deleting the older ones is beyond me. It eventually just eats up your /cache and slows Market Updates.
From what I can tell, there is absolutely no harm whatsoever in deleting these. You can delete them using Root Explorer + Multi-select or you can boot into Recovery and Wipe Cache. I am not sure if wiping /cache also clears Dalvik Cache if it is on /cache. However, if your phone takes a long time to reboot after wiping /cache then I would assume it does since your phone has to rebuild Dalvik. Either way, nothing is damaged.
I have looked at the various "cache cleaners" on the Market and have not found one that clears out these "Download-#.apk" files. If someone knows of one, please share it with the room.
The act of going into Applications and clearing MikMarket Data & Cache does NOT delete these extraneous files.
CONCLUSION:
If your Market is being unresponsive, use:
1. Root Explorer to delete all of the "Download-#.apk" files from your /cache (root), or
2. reboot into recovery and wipe cache.
After this, your Market should become much more responsive. Option #1 is easier.
Defy Froyo 3.4.2 Cookie Cutter Rom
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.
um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you
this Zip File is for what ?
Thanks
Greetings
you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App
So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse
eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.
what exactly is the benefit of this new method?
drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx
drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene
I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App
psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market
Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App
For experienced users only.
First of all props to roebeet for coming up with this idea over at the gTablet thread here.
This 'Recovery Pack' will install AmonRA-v1.6.2 and ClockworkMod-2.5.0.7 binaries in a folder 'recovery' created in /system/etc and 2 shell scripts in /system/bin used to call flash_image and flash the recoveries from Terminal Emulator.
How to use:
1. Flash the Recovery Pack
2. In Terminal Emulator:
$su
#amonrecovery.sh ~ for AmonRa-v1.6.2 Recovery
#cwmrecovery.sh ~ for ClockworkMod-2.5.0.7 Recovery
As you can see there's minimal typing and easy to remember names.
If you like you can add/replace recovery images in the /system/etc/recovery folder and create/adjust the shell script.
HeroC-Recoveries-signed.zip ~ Just the 2 recovery images and 2 shell scripts.
md5: 7414ee444eea7bdbf1e85e2ac89d7b86
HeroC-Recovery-Pack-signed.zip ~ Same as above but also installs flash_image in /system/bin.
md5: 936c949548de760ea2c135dccf0d60f8
As always Nandroid and proceed at your own risk. (read first line)
cant you do the same thing through rom manager this seems kind of pointless rom managers actually better to because u dont have to mess with TE.
I don't use ROM Manager all that much myself (GTablet doesn't play nice with it), but I assume you'd need an active Wifi connection to get the download, in case you wanted it? And what if the download site itself was offline? The scripts are more convenient, imo - you know that it will work since it's local, and it's pretty fast to run them. Terminal Emulator is a pretty good app to have, anyway.
And, it will always be the same version each time - which could be a good or a bad thing, depending on your needs of course. But options are always a good thing.
Bierce22 said:
cant you do the same thing through rom manager this seems kind of pointless rom managers actually better to because u dont have to mess with TE.
Click to expand...
Click to collapse
You can, but what if you can't boot in to the rom or you borked your recovery?
thats true i guess.
ill keep my mouth shut on these things for awhile ive already had enough shouting matches for one day lmao.
aiwetir said:
You can, but what if you can't boot in to the rom or you borked your recovery?
Click to expand...
Click to collapse
Well if you can't boot into the rom then you can't use terminal emulator either
Sent from my HERO200 using XDA App
trip187 said:
Well if you can't boot into the rom then you can't use terminal emulator either
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
adb
10characters
Bierce22 said:
thats true i guess.
ill keep my mouth shut on these things for awhile ive already had enough shouting matches for one day lmao.
Click to expand...
Click to collapse
I just had a shouting match on Facebook so I'm probably a bit grumpy, I should have said:
"Yes, you can do these things in ROM Manager, but if you can't boot into the rom or recovery, you can use these same scripts with ADB. I've had a hard time finding flash_image in the past so this whole pack is probably useful if you are in deep poo with your phone."
jazzruby said:
As always Nandroid and proceed at your own risk. (read first line)
Click to expand...
Click to collapse
I agree with that and this tool. Rom manager isn't better than this just because the server could be down, you have to download the recovery for the first time, etc, etc. Not saying its bad because I used to use it but now I use this if i'm on mobile and adb shell if on computer. Thanks
Thanks for this to all involved. I doubt I'll ever need it since I'm s-off, but it's a pretty awesome tool! I'm sure it will be useful to other users, I will link them to your thread
http://www.mediafire.com/?5dxoef8ib247ena
would you mind making a zip for your red theme to work on ef02 instead?
Maybe I'm missing something. A su that works for all apps... for gingerbread...What?
Noting the snippets from your updater-script (you might want to edit this in the future)
Code:
ui_print("Superuser 2.3.4 for Eclair/FroYo");
ui_print("Written by: ChainsDD");
su really hasn't changed much from eclair-gingerbread.. it's nearly the same binary just patched for a few different file system here and there.
Leaves me to ask again, working su? They all work.
If you want to link to anything, don't just link to an arbitrary updated superuser.
There's a huge problem with this as super user is signed by a public key that everyone has access too. Without having a hardcoded pid for the specific service, anyone on the market or any "developer" can grab said key, sign another malicious utility with it and brick nearly every android device.
But that's irrelevant as I don't even see you getting that far. I'm just confused by this post as it has 1) no detail 2) holds no merit.
actually to be fair its chain's from his post.. i snagged it and renamed it su.zip for the nexus s 4g one click. when i was testing rroting ef02 i uploaded just the zip.. its posted in that thread.. so decad3nce please forgive me.. ill try to kang better next time ;P
you guys dont understand, the old su.zip didnt have sh
sh? you mean that file thats on android to begin with? thats how oh.. EVERYTHING runs? trust me ive seen the effects of a phone without sh... there is no reason to add it in... unless its bash sh you're nicely replacing stock sh for everyone?
marcus your website is down
No. I had some problems with root in my rom because of a bad /system/bin/sh/
Sent from my SPH-D700 using XDA App
sounds like an error with the rom. not android
sounds like an error with the rom. not android
Click to expand...
Click to collapse
On this new release some people were complaining about root not working on done apps.same problem with my v6 rom. I applied the same fix.
Sent from my SPH-D700 using XDA App