-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Help for dead USB port?
- Thread starter uminchu
- Start date
-
- Tags
- htc evo 4g
Mr. Ed
Extreme Android User
we can fix that...I will find the thread if I have time later today
evomattnc
Android Expert
uminchu
Android Enthusiast
I'll be looking forward to that, thanks. I'm having a minor issue with ROM Manager/CWM on the new Evo that I wonder might be related to the bootloader.
When I rooted the new phone, Unrevoked flashed CWM, and I flashed Kings GB with it. The next day I realized I'd forgotten to update my PRL before flashing an AOSP ROM. So I ran ROM Manager, flashed RA 2.3 to reset, clear cache and Dalvik, and I restored Myn 5. I seem to be stuck in Amon now; I can't flash CWM anymore, at least through ROM Manager (haven't tried ADB yet). RM says it's there, but booting into recovery still brings up RA 2.3. Amon is fine (some ways better), so no big deal. I miss the convenient RM/CWM feature of assigning custom labels to nandroids, but I can always rename Amon backups afterward.
Has anyone seen a scenario similar to this? Is it the bootloader? Thanks.
novox77
Leeeroy Jennnkinnns!
Wow, first time I've heard someone report that a tech systematically checks for evidence of root. Good to know.
Don't mean to hijack this thread but.... Is it still possible to put the old .76 Eng HBOOT on an Evo that comes shipped with the current/latest OTA stock ROM? That would be my preferred way to have full root if I ever had to do what uminchu went through.
-edit- or maybe I wasn't so off-topic after all.
Mr. Ed
Extreme Android User
here it is...[GUIDE] HBOOT 2.10(.02 -?)[</3] Got you Down? - Get 0.76[<3] Back! - xda-developers
prolly just a savy tech... I wouldn't be too worried but as always...one should fully unroot when taking the phone in...better safe than sorry
here..I gave it a post over here
http://androidforums.com/evo-4g-all...ot-2-10-02-get-0-76-eng-back.html#post2737592
yeah rom manager will not work with amon ra. it is the front end of clockwork mod. so once you switched you cannot use rom manager anymore other then downloading roms. flashing will have to be done in recovery. just make sure when you name it that you do not use any special characters or spaces.
uminchu
Android Enthusiast
I understand all that, my problem is that I can't seem to flash CWM back, at least thru RM. RM says CWM is the current recovery, but it still comes up in Amon. I guess I'll have to try ADBing it in. If that doesn't work, I'll try flashing it via a PC36IMG from HBoot. Is the 2.10 HBoot causing this?
rom manager cant flash anything because you have amon ra. rom manager is the front end clockwork mod. rom manager can exist without clockwork mod but it cant flash anything. so to switch you need to get clockwork mod via a PC36IMG file. you can get it in ref#1 of my sig.but why again do you want to switch? amon ra is a much better recovery? if you are going back to cwm i would go with clockwork mod 2.6.
uminchu
Android Enthusiast
I agree with you. I also agree that overall, Amon is a better, more robust recovery. That said, CWM has a couple features that I really like, such as the ability to automate pre-labeled nandroids from ROM Manager, reboot and all.
When I rooted the new phone, Unrevoked3 installed CWM. I then installed RM. From RM, I flashed Amon RA 2.3. On my old phone, I could interchange them at will with a simple tap in RM. If I was able to flash Amon from RM on this new phone, why can't I get CWM back the same way? I've tried clearing the download cache, and flashing new and old versions of CWM from RM. RM reports the flash was successful and the current recovery is CWM, but rebooting to recovery still brings up Amon.
So what changed? Hardware? HBoot? Would it help to install RM as a system app instead of a user app? Any thoughts, ideas or suggestions appreciated.
no, that will help. rom manager needs clockwork modto flash things. since you have amon rait cannot do it. not sure why rom manager thinks it still has clockwork mod and it does not. really the easiest way to switch is to have the PC36IMG file. you can just have both files for amon ra 2.3 and cwm2.6 on the root of your card. just rename them so that hboot wont be confused. just name one of them correctly and reboot to hboot to switch recoveries.
novox77
Leeeroy Jennnkinnns!
I would try using the fastboot utility and manually flashing the recovery partition. Here's my notes from last summer:
If current recovery and OS is broken or needs replacement, use the HBOOT FASTBOOT to flash the recovery image. Make sure phone is plugged in via USB (w/ android hboot drivers installed on the PC). Make sure phone is at the FASTBOOT USB screen. Rename the .img file to recovery.img. From PC, go to the Android SDK's Tools folder. Put recovery.img in this location. From a cmd window at currentdir, run:
fastboot flash recovery recovery.img
Only thing is, I'm not sure if the fastboot.exe file is still in the /tools folder. I think some stuff got moved in newer SDK installations. Seems like these days, people package the .img into the PC36IMG.zip and have HBOOT just auto-flash stuff, which works just as well.
uminchu
Android Enthusiast
Sounds like a good idea. If I remember from my Hero days, it doesn't *have* to be named "recovery.img". Woildn't it still work if I kept multiple recoveries in the card's root folder, name them recovery_amon23.img, recovery_cwm3005.img (or 2601, etc), then use the specific names in the fastboot command?
yeah you can just keep them on the root of your card. just name them differently. I would keep the PC36IMG part and just add the amon ra part. And when you want to switch just delete the amon ra part.