• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[recovery]new recovery img v1.6.2

ok so i did the radio and new fresh rom now how would i do this do i flash it im gonna wait till i get an answer.


EDIT:read more about it and im guessing i do it through cmd...i guess i'll try and see how it goes.

EDIT EDIT:when i go through cmd and type adb it says adb is not recognized as an internal or external command...


EDIT EDIT EDIT:do i really need this or is this optional cause im really not getting it...
 
Upvote 0
well, since I didn't get an answer on XDA, I'll ask here.

What's the big difference between this and 1.5.2? Besides the disgusting carebears lol
- Added power off menu item
- New unyaffs binary patched by Koushik Dutta and Packetlss to fix the "losing root"-issue and incorrect file-time after a Nandroid restore
- New dump_image binary (by Brainaid) patched by Packetlss to fix the "bad blocks"- Nandroid restore issue.
(This will not fix old corrupted Nandroid backups! Please make new backups!!)
- New mkyaffs2image binary
- New flash_image binary
- Updated busybox to v1.5.3
- Nandroid menu options will NOT backup or restore recovery, cache, misc, splash1+2 (to avoid issues)
- Fixed wipe option not wiping when ext was not present
- Created carebear versions after the idea of packetlss
- Switched the Nexus logo to a Green Carebear with Nexus One logo (Thanks Montalbert!)




and you dont have to get a care bear version he has a normal green one with htc logo ;)
 
Upvote 0
- Added power off menu item
- New unyaffs binary patched by Koushik Dutta and Packetlss to fix the "losing root"-issue and incorrect file-time after a Nandroid restore
- New dump_image binary (by Brainaid) patched by Packetlss to fix the "bad blocks"- Nandroid restore issue.
(This will not fix old corrupted Nandroid backups! Please make new backups!!)
- New mkyaffs2image binary
- New flash_image binary
- Updated busybox to v1.5.3
- Nandroid menu options will NOT backup or restore recovery, cache, misc, splash1+2 (to avoid issues)
- Fixed wipe option not wiping when ext was not present
- Created carebear versions after the idea of packetlss
- Switched the Nexus logo to a Green Carebear with Nexus One logo (Thanks Montalbert!)




and you dont have to get a care bear version he has a normal green one with htc logo ;)

lol, thanks...that's all greek to me, but I get the gist.

I bit the bullet and updated it a bit ago anyway, right before you posted this lol
 
Upvote 0
Notice any change? I don't know if it's really worth it.

visually? no. I have no idea if it makes much of a difference or not. I'm sure it does, or they wouldn't have bothered to put it out there.

By what 702droid posted, it basically fixes some errors in the 1.5.2 version, or at least optimizes what's already there (I think? lol)
 
Upvote 0
visually? no. I have no idea if it makes much of a difference or not. I'm sure it does, or they wouldn't have bothered to put it out there.

By what 702droid posted, it basically fixes some errors in the 1.5.2 version, or at least optimizes what's already there (I think? lol)
;)
Should not mess up with 1.5.2 nandroid backups right?
nope they will be fine
 
Upvote 0
i reboot into recovery and try to flash the new image but it doesent show up just still goes to 1.5.2 any insight...and yes i have the new recovery img on the root of my sd as well

re-read the instructions. It's not a flashable update, you've got to push it via adb:

Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
Open a cmd prompt and enter:
cd c:\android-sdk-windows\tools (assuming that's where you've got it saved)
adb shell
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
 
Upvote 0
my bad i should have been more clear im not tryin to flash the file i mean flashing it through adb but after those commands it doesent say anything and when i reboot it it goes to 1.5.2 again. would it matter if 1.5.2 was still on the root of my sd card along with 1.6.2? (i just never got rid of it after i rooted)

I had some problems getting the 1.6.2 recovery as well, what I ended up doing was going through the whole root process and recovery installation process over again (using 1.6.2 instead of the 1.5.2 the instructions calls for) even though I was already rooted and I got the 1.6.2 installed.
 
Upvote 0
Well I can tell you that it does not unroot your phone doing it again, as I just did it on Monday :)

I was getting a "mounting dev block mmcblk0p2 on system sd failed no such file or directory" error when I ran the 'mount -a' command in adb (to install the new recovery) which is why I decided to go through the whole root process again. which happened to work

Good luck
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones