my hero was flashed my recovery to RA 1.2.3 by flashrec and flashed to modaco 2.8 core chinese. i would like to update to recovery 1.5.2 now, but when i open flashrec that doesn't allow me to flash it. what can i do? and any different with 1.2.3 and 1.5.2? last question is, is it my hero was rooted already? if not, what i do to root my hero? thx
Follow the link:
http://forum.xda-developers.com/showthread.php?t=561124
on the Install part.
If your hero not rooted how will you able to install recovery & flash mdc2.8?
If you need SDK tools pls download from here: http://developer.android.com/sdk/index.html
i know what you mean. but when i get into cmd in windows, i can't upgrade via adb or adb+fastboot. can you tell me what tools i have to download or send me the link which can teach me? because my english is worse, so maybe i was miss something when i was installing the custom rom. thx for your help.
As for the SDK i suggest download 1.5platform.
install into your C:\AndroidSDK
link up your mobile with usb cable to your pc.
Goto start -> run -> cmd
Code:
cd\
cd AndroidSDK\tools\
adb shell
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.5.2.img
According to: http://forum.xda-developers.com/showthread.php?t=561124
If you have an ext4 partition issue
Code:
tune2fs -E test_fs /dev/block/mmcblk0p2
Related
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
Okay, seems like you're not rooted yet. If that's the case, try the following site...
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
It gives pretty easy instructions on how to put the recovery image on and root the Hero.
After that, try the following link to put a custom ROM on your Hero...
http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
Cheers also had problems with rooting as well. I thought with the MoDaCo custom romyou didn't need a route. The FlashRec.apk seems to be a zip file not a .apk file so it wouldn't show up like it did on the video demo. on my sd card its still a zip.
Sorry just seen that I posted this thread in dev. Here is the same thread in Q&A http://forum.xda-developers.com/showthread.php?p=4516136#post4516136
If your a Mod please delete
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
coby kyros mid8048-8 stucks on start up logo screen after rom update can anyone tall me what to do o thing to make a sdcard boot but i dont know how pls helppppp.tnks
i have a tmobile g2 and used visionary to root and it did not work right but my s-off and i can not root any way i try,if i have stock rom what do i have to do to reinstall the stom rom and will this make my g2 go back to s-on?
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
renn9420 said:
There is a guide to all this called super cid and radio s-off in Android Developement might be able to help plus links.
If you have is s-off you can try to go to Menu - Settings - Applications - Manage Applications and go to tabs at top and press All. Then scroll down until you see Superuser and press it. Unistall it and do the same for Visionary. Then press home and try reinstalling Visionary and see if it works. First check the box that say make system r/w .sh or something then temp root. Once done then try to perm root. If you go to theunlockr.com and search how to root G2 you will find video and written instructions step by step.
Phone: T-Mobile G2/Vision Rooted/GFree'd
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
iv tried that and nothing works at all,i was told i needed s-on again because s-off is what i have and no matter what i try i can not root this **** phone!!!!!!im ready to throw it out the window.
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
steviewevie said:
Remove Visionary and try the "rage" method instead - http://forum.xda-developers.com/showthread.php?t=834228 - except in that guide, do not do the step that tells you to do "dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18". Do all the rest though.
If you haven't got adb working from your PC yet, follow this guide first to get adb going - http://forum.xda-developers.com/showthread.php?t=865685
Click to expand...
Click to collapse
im about to try it
hightechlive said:
im about to try it
Click to expand...
Click to collapse
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
hightechlive said:
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
Click to expand...
Click to collapse
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
steviewevie said:
Did the temp root bit go ok ? Did you get a root shell from running rage, with the "forked xxx children" message. Becuase those messages you posted are from the "root" script, and they indicate that rage isn't running.
Click to expand...
Click to collapse
yes i did get forked xxx children message,but i this is different for me
init_module 'wpthis-OTA.ko' failed
i get this
local/tmp/init_module 'wpthis-OTA.ko' failed
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
fastludeh22 said:
Here, this will tell you exactly what to do:
http://forum.xda-developers.com/showpost.php?p=9284754&postcount=187
Click to expand...
Click to collapse
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
hightechlive said:
having trouble with is
Guys if your s-off you've already won the battle. All you need to do is go the the clockwork mod recovery thread. Grab the recovery that says for manually flashing from fastboot. Put that img on the root of your computers c drive named recovery.img. then download rom of your choice, I suggest starting with my stock w/root rom, and put it on the root of your sdcard.
im getting a error when trying to unzip the file and where is the root of my computer c drive?
Click to expand...
Click to collapse
*Following instructions in that post includes a wipe. This will delete settings, 3rd party apps, mms etc. Be sure to backup what's needed.
These directions are for windows computers:
Do not unzip the file. It should be clockwork recovery 2.x.x.x.img. just rename it recovery.img. The root of c just means not in any folders. So after naming it recovery.img put it on c. It will then be c:\recovery.img
Then when you open up cmd window, goto sdk folder like when you use adb. With your phone booted into hboot with usb connected. You type this into cmd window: "fastboot flash recovery recovery.img" without the quotes. Then finish following pervious link.
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
i type in command window but it says can not load recovery img
hightechlive said:
goto sdk folder like when you use adb?HOW do i get in to sdk as i know how to get into adb?
Click to expand...
Click to collapse
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
fastludeh22 said:
From the link you said you followed, I assumed you have adb installed and have used it. If not you will have to look up how to install/use adb. When you install the sdk adb and fastboot are part of it. If fastboot is not included you can find it around page 19-21 of the rage root thread we been referenceing...
For refrence to get to folders you use cd command. So if you install sdk in folder called android on c drive. From cmd window it would be: cd.. (enter) cd..(enter). Till you were at c:\ . Then cd android (enter) cd sdk (enter) cd tools (enter) to get into tools folder. Then type fastboot commands...
Click to expand...
Click to collapse
i type in command window but it says can not load recovery img
im doing everything you said?
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
fastludeh22 said:
You have downloaded recovery from here?: http://forum.xda-developers.com/showthread.php?t=834731
The link that says to manually install.
Renamed that recovery.img
Copy and paste or screenshot of exact error message here.
Click to expand...
Click to collapse
i did that,this i what i did i download and change the name and put the zip file in the c root,open command and went to the tolls folder after the other things to get there in command and this is what it says
says can not load recovery img
What zip file? The recovery should be an img file.
fastludeh22 said:
What zip file? The recovery should be an img file.
Click to expand...
Click to collapse
that what im saying when i down load the file if is zip up and when i unzip it says i can not open it?
when i download it this is the name of the file
recovery-clockwork-2.5.1.2-vision (1)
I went to clockwork thread and clicked link. It dl's as .img file for me. This is the direct link I'm talking about. http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
If your using that, check this. In an open window/folder in windows. Click tools, then folder options. Select view tab. Uncheck "hide extensions of known file types". Then the file extensions should show at the end of every file. Make sure its named right now.
My HTC Desire has no USB functionality at all, including USB Fastboot. It's also got no root access. There's no known reason why this occured.
Similar forum threads suggest that USB functions can be restored if I revert to the stock RUU image. It's possible that an update has been the cause of this problem.
I've tried to install the base ROM - RUU, but because I have Hboot 0.93 I have to downgrade, but can't do that because there is no existing root access and I don't have ClockWorksMod recovery installed to get around the signature verifications.
The device boots up and operates fine (even the SD Card). I have to charge the battery using my partner's phone and can't do any data transfers. I'm running Android 2.2, Radio 32.49.00.32U_5.11.05.27, Hboot 0.93
I'm beginning to think that the motherboard has somehow been fried and can no longer supprt the USB part of it.
Any ideas would be most helpful. Thanks heaps
As you are unrooted, you should have warranty and that is the first way to fix it.
The other is a bit more complicated but if you are cautions, you'll be fine. Use this guide:
quanchi said:
...
This is a specific situation - usb brick and totally stock rom, recovery and hboot. It's not required for people who have a modified recovery and a rooted rom. It's easy like 1-2-3.
Before doing anything else enable the Debug Mode in the Applications / Dev menu
1. Download the rageagainstthecage exploit from the authors site:
http://c-skills.blogspot.com/2010/08/please-hold-line.html
2. Download the flash_image and misc (mtd0.img) partition image from this thread.
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
Modify the mtd0.img according to your phones CID (how to get the CID also explained in the thread)
2. Download Android Terminal Emulator from the Market
3. Copy the exploit binary (rageagainstthecage-arm5.bin), the flash_image and modifed mtd0.img to the sdcard via an external card reader
4. Start the Terminal
5. Copy the files to the Terminal app data directory (the only place on the data partition you will have write access while running the Terminal), and make the binaries executable
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/shared_prefs/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/shared_prefs/mtd0.img
cd /data/data/jackpal.androidterm/shared_prefs/
chmod 755 rageagainstthecage-arm5.bin flash_image
6. Run the exploit
Code:
/data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
After the exploit exits/finishes there should be a short system freeze, followed by inablity to issue any command from the terminal (don't worry). Exit the Terminal by long pressing HOME and force close the Terminal app from the Application Manager
7. Start the terminal again, a root prompt should be visible
8. Flash the misc partition
Code:
cd /data/data/jackpal.androidterm/shared_prefs
./flash_image misc mtd0.img
9. Reboot
...
Click to expand...
Click to collapse
No luck unfortunately, one of the steps requires the CID, and as you know I have not got USB to access fastboot mode.
Is there any other way to get the CID?
You should read the whole thread for the usb-fix
If I remember correctly you should use "cat /sys/class/mmc_host/mmc1/mmc1:*/cid" (without quotes) command from the terminal emulator.
The terminal emulator in your case will be the substitute for the fastboot, so everything is done via the former.
If you click the link to the quote, you'll see that there are number of people who got it sorted using this method. So just be patient and do the reading.
Ive got same problem, but have fastboot access.. Can I use regular terminal in windows then?
Well, you can use it to find the CID ("fastboot oem boot"), but the other commands in the guide quoted above are for a terminal emulator and are not the same as the ones used with fastboot. So in order not to get confused I recommend you to just use a terminal emulator, it's not harder than fastboot.
Well, i figured out that one on my own.. At least I learn something of this.. Anyway, when i try to execute first command in emulator I just get up "cannot create, directory nonexistent. Ive tripple checked the commandlines.. What could be wrong??
bump.........
Well I followed all the instructions, could get temp root access and flash a modified mtd0.img (which had the correct CID and Rom version) but still no USB. I tried it several times over and can't get anywhere. The hardware must be cactus! Time to throw it over a cliff !!
1 Im sorry for my english,im spanish
2 ive got superuser and i dont want this ,but i know that the solution is unroot but my defy JRDNEM_U3_3.4.311_BLUR_SIGN_SIGNED in superonclik i dont see option unroot,can you help me?
Thanks
Here's a quote from another XDA thread which can help you get rid of superuser without voiding the guarantee
XDA thread said:
adb shell
su
Step 6) If you get "permission denied" or something like that from step 5a/5b,
CONGRATULATIONS! YOUR PHONE HAS BEEN SUCCESSFULLY UNROOTED!
Step 7) If you don`t want to void your warranty, you should unistall applications that require root, especially Superuser
To date, I have rooted and unrooted my phone (Backflip) 3 times without any problems. In case your phone can`t be booted up, only to the bootloader or recovery, DO NOT WORRY! You can use the adb (android debug bridge) to flash in the stock recovery, push/pull the updates and reboot the phone into recovery mode or normal mode!!!
Useful ADB commands
Reboot Phone
adb shell
reboot
Reboot Phone into recovery mode
adb shell
reboot recovery
Flash a new recovery image temporarily (resets when rebooting)
adb shell
flash_image recovery /sdcard/recovery.img
Flash a new recovery image that does not reset when rebooting
adb shell
flash_image recovery /sdcard/recovery.img
exit
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Push file to sdcard
adb push file.blah /sdcard/file.blah
Push file to sdcard
adb pull /sdcard/file.blah file.blah
Click to expand...
Click to collapse
OR try this:
* The first step is to enable USB debugging mode on your device. You can enable USB debugging on your phone by going to Menu > Settings > Applications > Development and check mark USB Debugging.
* Now Download one click root file, extract the contents and save them on your desktop [or wherever your prefer].
* Now connect your phone to the computer and double click on Galaxy S I9000 One-Click Root file.
* Now simply click One-Click Root 2.1 or 2.2 on the screen and follow the onscreen command mode instructions to complete the root process. Please note that for One-click root 2.1, your phone needs to be running Android 2.2 2.1 Eclair and for One-click Root 2.2, Android 2.2 Froyo.
* In case you are using this application to unroot your phone then simply follow the instructions above and click on One-click Unroot.
Old superoneclick versions don't have unroot option. The new versions have. If superuser is still there after unroot, you can uninstall it like uninstalling other app.
Thanks every all but i dont want of new flash a,d log time i do z4root and has unroot and superoneclick no,the version old have goot unroot but this not,and remember ive got defy im not Galaxy I9000 S