http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk
IS FOR SPRINT. NOT GSM. BE ALERT
Sent from my Hero using Tapatalk
orangeclanz said:
http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
Nice to see the CDMA Hero has it's official 2.1 fame .. but come on lazy HTC, where is 2.1 for the GSM cousin? Let's hope tomorrow is THE day..
Looks like it's working
EDIT: However, this is exactly the same as Villain 5.2 (the same leak that is).
Pretty stable
It does work well.. What an improvement from the previous version
HomerSp said:
Looks like it's working
Click to expand...
Click to collapse
But not on GSM Hero's - grrrrrrrrrrrrrrrr
Didn't the GSM hero come out before the CDMA one? How come the CDMA one came out first?
hkr said:
But not on GSM Hero's - grrrrrrrrrrrrrrrr
Click to expand...
Click to collapse
It does if you port it (I only have gsm) ;-)
HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..
someonenewhere said:
Who can co-sign it?.
Click to expand...
Click to collapse
What?
I need a Mercedes? Can someone co-sign it?
Just playing
Old news >> http://forum.xda-developers.com/showthread.php?t=661057
All of our dev's 2.1 builds are already based on this build.
FYI, when the final (non-test) build .exe comes out, flashing your phone with it may render your phone unrootable.
someonenewhere said:
HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..
Click to expand...
Click to collapse
I put it on my Hero with no problems. My guess is its very close to the RC. Or he could just wait!!
Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.
Don't flash a ruu that doesn't have root. The exploits used to gain root are probably patched. Also this will over write your custom recovery. Leaving you with no way to flash custom roms. Wait until someone puts out a build with root.
tedya said:
Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.
Click to expand...
Click to collapse
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
danknee said:
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.
tedya said:
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.
Click to expand...
Click to collapse
you cant gain root in any other way now theres no known exploit for 2.1 yet so your basically screwed till someone finds a exploit next time gather information before you run some random program that hasnt even really been verified
Yeah, I have learned my lesson I think. I think I am going to wait around until there is an exploit for 2.1 before I end up bricking this thing. I ended up getting the flash_image pushed but now I can't reboot and use the recovery image. It goes straight to a HTC with red triangle and red exclamation point. Luckily I was able to do a battery pull and it rebooted straight to the RUU 2.1 ROM. I thought I had bricked the thing. Whew! I'll see what some of the masterminds come up with here.
I think all I am missing is being able to go into bootloader and do the v1.6.2 recovery image and then flash a custom ROM.
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-a
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-after-using-2-1-ruu.html
This worked for me thanks to GBhil!
Thanks SooooneR! This worked for me. I am flashing one of DamageControl's ROMs right now. Very cool.
Related
Update: I'd recommend using the full update found here instead - it's less likely to fail than this one based on the patch update.
I've managed to build a working RC30 update that retains root via adb shell. Much of the credit goes to the people in this thread. All I did was build an updated boot.img with ro.secure set to 0, and reinsert it into the RC30 update.
Installing it will require the modded RC29 recovery image found in that thread.
A warning: if you've modified any files that are patched in the RC30 update, bad things will happen. Also, I had to disable the version check, so if you attempt to apply the update to anything but RC29, bad things will happen. I'm not responsible if your phone is bricked, bursts into flames, or even starts walking around on it's own and attacks you.
Modified RC30 update
did you have any trouble installing it? I will give it a try later today.
1 question, so theres no root on the phone Only by adb?
Edit:2 questions have you try to put busybox on?
It worked fine for me. Just follow the manual firmware update procedure, and it should work, as long as you're already running the modified RC29.
humble said:
1 question, so theres no root on the phone Only by adb?
Click to expand...
Click to collapse
Yeah, it closes the root console bug. However, once you have root via adb, you can do pretty much anything you want, including create a new suid root shell.
yes thats all i need to know disregard my edit
it dose not work I'm stuck! i got some sort of error
It won't let me mount the SD card... gonna ask in the other thread
What was the error exactly? Did it come at the recovery screen when you first tried to update, or later? Is your phone still working?
rale00 said:
What was the error exactly? Did it come at the recovery screen when you first tried to update, or later? Is your phone still working?
Click to expand...
Click to collapse
Thanks for asking the error was 105, yes later, and yes
and this is what i did
THANK GOD!! for JesusFreke Restore Original RC29 Boot Image.zip. if what happened to me happens to anyone just rename that file up above to update and your golden.
Note: i used it and now i have
kila-user 1.0 TC4-RC30 116143
ota-rel-keys,release-keys
i dont understand... and i sill have root on my phone and busybox, and telnetd exploit still works
maybe i should try it again?
It sounds like the update partially completed for you, since it claims to be RC30, but it failed either sometime before or during the flash of the updated boot.img. boot.img has the fix for the telnetd exploit, which is why it's still working for you after restoring the RC29 version.
If you try to run the RC30 update again, it will probably fail, since some or all of your other files are already updated.
The bad news is, you probably won't be able to install any future updates with the state you're in now. What you probably want to do now is try to figure out how far along in the update script it failed.
If you can download the following files off your phone, and post them somewhere, I'll compare them to the versions in a completely updated RC30 and should be able to get a better idea of where you are.
/system/framework/android.awt.jar
/system/app/GoogleSearch.apk
/system/app/Bugreport.apk
What good thing i made a backup of my flash i am going to see if i can restore it using this methodhttp://forum.xda-developers.com/showthread.php?t=442831
but witch partitions should i flash? and is it a good idea
rale00 said:
/system/framework/android.awt.jar
/system/app/GoogleSearch.apk
/system/app/Bugreport.apk
Click to expand...
Click to collapse
how do i get them to the sdcard? i will post them
I can get root through adb shell after this, which is fantastic!
So I try this from adb shell:
cd /system/bin
echo sh > su
chmod 4755 su
But when I run su from the phone's terminal, I don't get a root shell. (reboot gives me a reboot: Operation not permitted.
Any ideas?
humble said:
What good thing i made a backup of my flash i am going to see if i can restore it using this methodhttp://forum.xda-developers.com/showthread.php?t=442831
but witch partitions should i flash? and is it a good idea
Click to expand...
Click to collapse
Oh, that's good news. If you have a backup of mtd3 / "system", then you should be able to just restore that and be in good shape.
rale00 said:
Oh, that's good news. If you have a backup of mtd3 / "system", then you should be able to just restore that and be in good shape.
Click to expand...
Click to collapse
thanks, but i wanna help out with those files. and do you know the exact commands to copy(i know cp and"???? ") and to restore mtd3
SORRY........
to restore is this right....
cat /dev/zero >> /dev/mtd/mtd3
flash_system /sdcard/mtd3.img
To copy them to sd card:
cat /system/framework/android.awt.jar > /sdcard/android.awt.jar
cat /system/app/GoogleSearch.apk > /sdcard/GoogleSearch.apk
cat /system/app/Bugreport.apk > /sdcard/Bugreport.apk
I haven't tried this, so I don't know if it works, but to restore system, if you backed it up using the directions in the other thread, should just be:
flash_image system /sdcard/mtd3.img
I wouldn't recommend cat /dev/zero to it first, because flash_image is actually on the system partition.
rale00 said:
To copy them to sd card:
cat /system/framework/android.awt.jar > /sdcard/android.awt.jar
cat /system/app/GoogleSearch.apk > /sdcard/GoogleSearch.apk
cat /system/app/Bugreport.apk > /sdcard/Bugreport.apk
I haven't tried this, so I don't know if it works, but to restore system, if you backed it up using the directions in the other thread, should just be:
flash_image system /sdcard/mtd3.img
Click to expand...
Click to collapse
Thanks rale00, when im finish if it works i'l post
Only apply if you have a stock Roger's Magic without root!
The following procedure flashes the stock Roger's boot image with root access enabled to your Roger's Magic :
1. Copy this update to your SD-card.
2. Download RAv1.0's rooted recovery here.
3. Boot the device in fastboot mode.
4. Connect the device to your machine over USB.
5. $fastboot boot recovery-RAv1.0H.img
wait a few minutes and unplug your device from USB
6. Choose option "Apply sdcard:update.zip" from the menu
If the flashing doesn't work you might need to flash this SPL update from your sd-card after fast booting with recovery-RAv1.0H.img
If you want to have a rooted recovery as well, you can check out this post.
Enjoy
Special thanks to :
Haykuro for all his help ^^ , buy him a Nesquik!
JesusFreke for his JFv1.43's recovery
Would this work on the Rogers Dream?
alritewhadeva said:
Would this work on the Rogers Dream?
Click to expand...
Click to collapse
No it would not work.
It works! Woot Root!
Edit: Confirmed root adb access by pushing these onto my phone. Now my Rogers is more awesome! Huzzah!
how do i do the fifth step
"5. $fastboot boot recovery-RAv1.0H.img"
when i connect in fast boot method, i get a a found new hardware dialog box running windows vista ultimate x64 eition
trincisor said:
how do i do the fifth step
"5. $fastboot boot recovery-RAv1.0H.img"
when i connect in fast boot method, i get a a found new hardware dialog box running windows vista ultimate x64 eition
Click to expand...
Click to collapse
Did you install the drivers properly?
Now we need to get more roms working with the Rogers! Any ideas on how we con go about that?
is there any reason that this wouldn't work on the Dream ?
jpa- said:
is there any reason that this wouldn't work on the Dream ?
Click to expand...
Click to collapse
1. I don't think the kernel inside the recovery image would work on the dream.
2. The boot image inside the update is from the Magic, not from the dream.
There's no harm in trying to fastboot the recovery image... but I don't think it will work. Let us know if it would!
Don't we need rooted recovery to be able to restore our backups? Just confirming......
parrot5 said:
Don't we need rooted recovery to be able to restore our backups? Just confirming......
Click to expand...
Click to collapse
recovery-RAv1.0H.img is rooted...
Wow... Thanks Amon_RA! I can now install some input methods that I couldn't do...
We still can't just choose any ROM out there, correct? Or now that we have ROOT we are invincible? .. hehe
Here's another possible noobish question: there doesn't appear to be any su installed by default into the stock Rogers rom (ie. attempting to su from the console results in "su:not found"). Any ideas?
parrot5 said:
Wow... Thanks Amon_RA! I can now install some input methods that I couldn't do...
We still can't just choose any ROM out there, correct? Or now that we have ROOT we are invincible? .. hehe
Click to expand...
Click to collapse
The boot images inside the "any ROM" would have to be repacked using Haykuro's discovered offset
So make sure you know what you are doing and always make a backup of your current configuration first!
Any specific ROM you would like to run on your rooted Rogers?
skittleguy said:
Here's another possible noobish question: there doesn't appear to be any su installed by default into the stock Rogers rom (ie. attempting to su from the console results in "su:not found"). Any ideas?
Click to expand...
Click to collapse
Just download Koush's su from his blog here.
* Unzip the ZIP file (it will create a folder called Superuser).
* Run install.bat (or install.sh if you are on Linux) from the Superuser directory.
Amon_RA said:
The boot images inside the "any ROM" would have to be repacked using Haykuro's discovered offset
So make sure you know what you are doing and always make a backup of your current configuration first!
Any specific ROM you would like to run on your rooted Rogers?
Click to expand...
Click to collapse
Not sure I know what I'm doing I do not know how to mod an image.
I saw on the forum that a few people mentioned the Ion ROM is the fastest of the bunch? I definitely would want to try it. I know many other people who want the Hero ROM instead
Amon_RA said:
Just download Koush's su from his blog here.
* Unzip the ZIP file (it will create a folder called Superuser).
* Run install.bat (or install.sh if you are on Linux) from the Superuser directory.
Click to expand...
Click to collapse
Thank you so so much for all your work. You have truly made my month
wow it worked.. damn.. now i might have to get me a mytouch3g when it gets released
I followed the instructions and the phone rebooted... should I be able to su now?
I get permission denied..
thanks for your work on this Amon_RA & Haykuro!
All the best,
Rob
thank you for this.
i have a rooted rogers magic with su access.
wifi-tether is not working for me with the rogers rom. need to install a new rom i guess.
Howdy,
Reckon it's been a while since I posted something nice up but I reckon I'll give up some goodies....
I have for yalls pleasure the DG27 to D107 update directly from Sprint, got it on my phone a few minutes ago and pulled it off.
ALSO, I pulled some of the standalone goodies out of it for yalls pleasure as well. These include the media hub apk, and the included qik.apk.
Media Hub:
http://www.droidbin.com/index.php/files/get/HRIhXjP2UZ/mediahubv102-epic4g.apk
Qik:
http://www.droidbin.com/index.php/files/get/p7oQLsoZmp/qik.apk
DG27 to D107 Update (Original non-modified-Signed):
http://www.droidbin.com/index.php/files/get/iv_p2mYBQH/cec94babb124.update-dg27-to-di07.zip
So I through together an update.zip that works on any ODEXED Stock ROM Basically it throws the needed files into system/app and then performs the checks...this is for those with ClockWork Recovery. Be aware that this method requires the stock kernel as well.
Please make sure you do a backup before using this
Update.zip (for clockwork recovery and includes all the listed apps below)
http://www.droidbin.com/index.php/files/get/CynNhuAMDp/update.zip
Firon said:
These are all the files that need to live in /system/app before the updater will work. There's also some files in /system/framework it checks for, but if you removed those, you're probably in trouble
Code:
/system/app/AccountAndSyncSettings.odex
/system/app/AlarmClock.odex
/system/app/ApplicationsProvider.odex
/system/app/BluetoothOPP.apk
/system/app/BluetoothOPP.odex
/system/app/BluetoothServices.odex
/system/app/BluetoothTestMode.odex
/system/app/Brightness.odex
/system/app/Browser.apk
/system/app/Browser.odex
/system/app/BuddiesNow.odex
/system/app/CallSetting.odex
/system/app/Camera.apk
/system/app/Camera.odex
/system/app/CameraFirmware.odex
/system/app/CertInstaller.odex
/system/app/Contacts.apk
/system/app/Contacts.odex
/system/app/ContactsProvider.apk
/system/app/ContactsProvider.odex
/system/app/DataCreate.odex
/system/app/DeviceManagement.apk
/system/app/DeviceManagement.odex
/system/app/DialerTabActivity.odex
/system/app/Divx.odex
/system/app/Dlna.apk
/system/app/Dlna.odex
/system/app/DownloadProvider.odex
/system/app/DrmProvider.odex
/system/app/DrmUA.odex
/system/app/Dun.odex
/system/app/Email.apk
/system/app/Email.odex
/system/app/EnhancedGoogleSearchProvider.apk
/system/app/FactoryTest.odex
/system/app/FlashPlugin.apk
/system/app/FlashPlugin.odex
/system/app/FlashSVGPlayer.apk
/system/app/FlashSVGPlayer.odex
/system/app/Gallery3D.apk
/system/app/Gallery3D.odex
/system/app/GlobalSearch.odex
/system/app/Gmail.apk
/system/app/GmailProvider.apk
/system/app/GoogleApps.apk
/system/app/GoogleCheckin.apk
/system/app/GoogleContactsSyncAdapter.apk
/system/app/GooglePartnerSetup.apk
/system/app/GoogleSearch.odex
/system/app/GoogleSettingsProvider.apk
/system/app/GoogleSubscribedFeedsProvider.apk
/system/app/GpsSetup.odex
/system/app/HTMLViewer.odex
/system/app/HiddenMenu.odex
/system/app/InputEventApp.odex
/system/app/JobManager.odex
/system/app/KeyBoardSlideUpCounter.odex
/system/app/Keytracer.odex
/system/app/LatinImeTutorial.apk
/system/app/Launcher.apk
/system/app/Launcher.odex
/system/app/LiveWallpapers.odex
/system/app/LiveWallpapersPicker.odex
/system/app/LogsProvider.odex
/system/app/Maps.apk
/system/app/MarketUpdater.apk
/system/app/MediaProvider.odex
/system/app/Memo.odex
/system/app/Mms.apk
/system/app/Mms.odex
/system/app/MobileAP.apk
/system/app/MobileAP.odex
/system/app/Music.apk
/system/app/Music.odex
/system/app/MyFiles.apk
/system/app/MyFiles.odex
/system/app/NetworkLocation.apk
/system/app/OtaProvisioningService.odex
/system/app/PackageInstaller.odex
/system/app/Phone.apk
/system/app/Phone.odex
/system/app/PhoneCrashNotifier.odex
/system/app/PhoneErrService.apk
/system/app/PhoneErrService.odex
/system/app/PhoneInfo.odex
/system/app/PicoTts.odex
/system/app/SamsungWidget_CalendarClock.odex
/system/app/SamsungWidget_FeedAndUpdate.odex
/system/app/SamsungWidget_ProgramMonitor.odex
/system/app/SamsungWidget_StockClock.odex
/system/app/SamsungWidget_WeatherClock.odex
/system/app/SelectiveReset.odex
/system/app/Settings.apk
/system/app/Settings.odex
/system/app/SettingsProvider.apk
/system/app/SettingsProvider.odex
/system/app/SetupWizard.apk
/system/app/SisoDrmProvider.odex
/system/app/SnsAccount.odex
/system/app/SnsProvider.odex
/system/app/SoundRecorder.odex
/system/app/SprintTV.apk
/system/app/SprintZone.apk
/system/app/Street.apk
/system/app/Swype.apk
/system/app/TATLiveWallpapersDandelion.odex
/system/app/TATLiveWallpapersLuminescence.odex
/system/app/TATLiveWallpapersOceanWave.odex
/system/app/Talk.apk
/system/app/TalkProvider.apk
/system/app/TelephonyProvider.odex
/system/app/TouchWiz30Launcher.odex
/system/app/TouchWizCalculator.odex
/system/app/TouchWizCalendar.odex
/system/app/TouchWizCalendarProvider.odex
/system/app/TtsService.odex
/system/app/UserDictionaryProvider.odex
/system/app/Vending.apk
/system/app/VideoPlayer.apk
/system/app/VideoPlayer.odex
/system/app/VoiceDialer.odex
/system/app/VoiceSearchWithKeyboard.apk
/system/app/VpnServices.odex
/system/app/WiMAXLineTest.apk
/system/app/WlanTest.odex
/system/app/amazonmp3.apk
/system/app/audioTuning.odex
/system/app/gtalkservice.apk
/system/app/lcdtest.odex
/system/app/serviceModeApp.odex
/system/app/shutdown.odex
Click to expand...
Click to collapse
Download this to get these back:
http://www.megaupload.com/?d=20HJ9004
ENJOY!
images arent loading, opening them in a new tab brings up droid bin
Your too fast
So we can flash this .zip in clockwork recovery and get the whole update?
meh I cant guarantee that will work. My bet is that you will get a signature error...If someone takes this and signs it with the test keys then it may work...depending on what kind of checks it does....
why cant you flash with the stock recovery if it is signed?
Looks like it does a system integrity check and if it fails the checks, any of them, then it wont update your phone...for instance, I tried to install the new update but it fails because I have the 3.0 TouchWhiz launcher
Stericson said:
Looks like it does a system integrity check and if it fails the checks, any of them, then it wont update your phone...for instance, I tried to install the new update but it fails because I have the 3.0 TouchWhiz launcher
Click to expand...
Click to collapse
I am pretty sure the clockwork recovery that noobnl got working has an option to bypass checks or signing but not sure if it actually works. TW 3.0? Gimme some lub here
thanks for the file- I just renamed it "update.zip", placed it on the root of the SD card and used the stock recovery.
I did this after I had gone back to the completely original stock using odin. Tested using mediahub which now loads- under build # I see D107 now
Here is the pastebin of the script....
http://pastebin.com/MVyryDTd
The actual script:
http://www.droidbin.com/index.php/files/get/rDpoTiSQD7/updater-script
jimmyz said:
thanks for the file- I just renamed it "update.zip", placed it on the root of the SD card and used the stock recovery.
I did this after I had gone back to the completely original stock using odin. Tested using mediahub which now loads- under build # I see D107 now
Click to expand...
Click to collapse
how do u get to stock recovery?
Kapow, here is an update script that runs no checks what-so-ever
http://pastebin.com/04EwkdJG
But you need to know whats different on your system because if they try to patch something on your system thats different then what they are suspecting then baaaaad things can happen.
Honestly it wouldnt be hard to make a working update for root users from this....
Stericson said:
Here is the pastebin of the script....
http://pastebin.com/MVyryDTd
The actual script:
http://www.droidbin.com/index.php/files/get/rDpoTiSQD7/updater-script
Click to expand...
Click to collapse
What do we do with this again? Or how can we apply it Stericson? Thanks.. I'm so used to HTC I am getting the hang of this new way..
plmiller0905 said:
how do u get to stock recovery?
Click to expand...
Click to collapse
assuming you dont have a custom recovery loaded just turn off the phone completely and then power on while holding down volume down and camera button.
Basically to make this work for everyone...simply have someone apply the stock update.zip, then get the patched files from their phone and make a update.zip signed with test keys to give you the patched files...
or, revert to nearly stock, meaning using all the exact files they are using and just apply this update.zip after signing it with the test keys...
jimmyz said:
assuming you dont have a custom recovery loaded just turn off the phone completely and then power on while holding down volume down and camera button.
Click to expand...
Click to collapse
Jimmyz I totaly forgot about this.. This is tech the other "official" way to update the device. As this is what ti does after the download to cache. I am liking the ease of one clicks and etc with Samsung.. This could be better than HTC's click and flash..
jimmyz said:
assuming you dont have a custom recovery loaded just turn off the phone completely and then power on while holding down volume down and camera button.
Click to expand...
Click to collapse
Thanks, which keys are used during stock recovery?
plmiller0905 said:
Thanks, which keys are used during stock recovery?
Click to expand...
Click to collapse
Hah- Im such a noob I dont know! How would I find out?
he didnt use any keys, the update.zip he used was signed by Sprint
jimmyz said:
Hah- Im such a noob I dont know! How would I find out?
Click to expand...
Click to collapse
ha...not noob by the way...but any ways...i got it figured out!
Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
after that i tried to mount the system from shell command but failed... then the phone got hanged and when i removed the USB cable it rebooted straight into recovery...
since the ive tried to check directory listing with adb ls /system command but it returns nothing... adb ls /data also shows only 3 files... i had taken a backup of /system using adb pull but i dont knw how much that'll help...
i did not take any backups before that... was trying to install CWM so that i could take rom backup....
im not able to boot the phone normally...
i would like to know if i can go back to original state?? if not is ther any other solution like flashing a new ROM or something...??
i would like to extract contacts nd messages if possible...
System config:
- Samsung Galaxy S 4G... everything stock
- Rooted!!
thanks in advance...
chi_visor said:
Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
Click to expand...
Click to collapse
'chmod 6 /system' did what you asked it to do. chmod, on a basic level, uses three (3) sets of permissions: global, group, and user. What you effectively did was set the user permissions to rw but blanked out everything else (like chmod 006).
If you can get into the shell, do this:
chmod 755 /system
That should put it back the way it was (7 = rwx for global, 5=rx for group, 5=rx for user)
See if that helps. Report back and let me know.
Real quick; I had my permissions backward. Although you still want 755 it should've read like this:
rwx for user
rx for group
rx for global
I had them backward.
Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??
chi_visor said:
Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??
Click to expand...
Click to collapse
I was worried about something like that. My guess is that your best bet is to see if you can get into download mode and flash a new ROM. Were you on Froyo or GB before? If you were on Froyo & you're trying to get to GB you'll need to insure you flash a ROM with the right boot loaders first, like chadster's KG4 (http://forum.xda-developers.com/showthread.php?t=1183413).
Let me know if I can be of help.
I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...
chi_visor said:
I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...
Click to expand...
Click to collapse
If your contacts were set to sync with Google or your carrier, then they will sync back to your phone after you flash. Given you were on Froyo, you can grab one of the Froyo ROMs from the bible (http://forum.xda-developers.com/showthread.php?t=1117554). Those will likely be rooted, deodexed, or something along those lines. If you want pure stock, you can grab that from samfirmware.com. You'll have to register to navigate to the firmware, though. I'd post a link but it wouldn't work right. Just go to the 'mobile' link and look for the SGH-T959V stuff. Either way, KD1 was the latest Froyo out there from Samsung.
Yup... I'll check on samfirmware.com..
sad abt contacts cuz dint sync the latest ones with google...
anyway i'll try the other method...
thanks..
Sorry man. Best of luck to you. Let me know if you get it fixed.
hi stephen_w,
I downloaded the T959VUVKD1 firmware from samfirmware.com....
I used odin to flash it...
after switchin on the phone in download mode... i flashed the firmware by browsing the file in PDA and leaving PIT, BOOTLOADER, Phone and CSC blank...
the process started and after cache.fs... below it was message:Complete(Write) operation failed.... it stopped nd showed fail in red...
i held the power key for a long time but then it started to show a phone linked to the computer with a yellow exclamation sign...
what does this mean?? im not able to boot into either recovery or download mode now...
please help...
ODIN will still see it when it looks that way, so don't fret! I had similar issues before but mine was a faulty download. Try using this one. It's not 100% stock as it's been deodexed, but it should work:
http://www.multiupload.com/7L5YDG8X8V
Ya im downloading tat one... Odin is detecting nd working... so i guess re-flashing should do the trick...
Jus to confirm I should leave fields other than PDA blank rite?
Yes, PDA only & let ODIN decide what should be checked.
Sent from my SGH-T959V using XDA App
Up and running jus like b4...
Thanks bro...
No worries; glad you're working again!
I need the flash_image that is compiled for the Sensation. If anyone is running a version of CM7 or any other ROM that has it. Looks like AHRD doesn't contain it...
If y'all wouldn't mind looking to see if you have it on your ROM and perhaps zipping it and uploading it for me it would be greatly appreciated.
It would be located in /system/bin
Code:
dd if=/system/bin/flash_image of=/sdcard/flash_image
will put it onto your sd card from adb or terminal emulater
http://dl.dropbox.com/u/9441929/flash_image.zip
TamCore said:
http://dl.dropbox.com/u/9441929/flash_image.zip
Click to expand...
Click to collapse
Thanks a bunch, hopefully it works for what I want. 15 minutes and I can hit d/b and download it... Stupid work with no cell signal lol
Worked wonderfully thank you
For those that were wondering what I needed it for it was so I could flash a recovery without a computer with just the android terminal
Sent from my HTC Sensation 4G using xda premium
using flash_image to change recovery, not working ...
I am on the road a lot, so I don't carry my pc in my pocket but I carry my phone.
So on to my problem.
I have tried all sorts of tutorials on how to do this properly and variants of it but whatever I do I cannot complete it.
What ? I want to flash any recovey I like using flash_image in Terminal Emulator
su
flash_image recovery /sdcard/recovery.img
and all sorts of other commands, but they all fail
At the moment I am on ICS 3.32.401.5
Could someone please present a method that actually work?