So has CWM Recovery been fixed? The whole not being able to charge the phone if the battery died. I would like as many people to chime in so I feel assured that it either has, or has not been fixed. The latest CWM Recovery that I am inquiring about is 5.8.1.4.
I still consider myself a n00b with this stuff, but it seems like I'm still having the same issues with CWM that everyone else is describing.
Most importantly for me, CWM freezes every time it tries to make a nandroid backup. I had the amon recovery, but I guess I installed CWM through the ROM Manager app, not realizing what I was doing. No matter, though, since I couldn't get amonto make a nandroid backup of my Rezound either.
So if anyone can help me figure out how to make a nandroid backup, that would be great ...
bloodymurderlive said:
I still consider myself a n00b with this stuff, but it seems like I'm still having the same issues with CWM that everyone else is describing.
Most importantly for me, CWM freezes every time it tries to make a nandroid backup. I had the amon recovery, but I guess I installed CWM through the ROM Manager app, not realizing what I was doing. No matter, though, since I couldn't get amonto make a nandroid backup of my Rezound either.
So if anyone can help me figure out how to make a nandroid backup, that would be great ...
Click to expand...
Click to collapse
I am not sure what version of Amon Ra you tried to flash or how, but are you on the new firmware or old ? Regardless, download the newest Amon ra recovery img and place it in the same folder as you used to unlock with.
Bring up a command prompt , and change directory if needed to the folder containing your image. Have phone connected in hboot so that it says fastbootusb ... then type in fastboot flash recovery "nameofrecovery".img
This will flash the recovery ...
In recovery just choose backup/restore...nand backup ..press power to confirm and it will make a backup.
mjh68,
Thanks for the info. I will probably try again when I get home. But since I had problems with amon last time, do you know where I can get the version of amon that I should be using for my Rezound?
Here's my software info:
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
If amon works better than CWM currently does, at least for nandroid/B], I will definitely let you know. Too bad CWM doesn't just work, though ...
Use 3.15, use scotts clean flashtool. It taked the adb commands out. You can find it on his website
Sent from my INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
Alright, I followed Scotty's "temporary recovery" instructions here: (darn, link not allowed for n00b's ... the title is "Scottys noob friendly root guide-start to finish" at androidforums)
These are the same instructions I used to root my phone in the first place.
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were, then selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection. It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
So now I'm stuck, and it looks like Amon is not working as an alternative to CWM.
I looked for Scott's clean flash tool, but I couldn't find it anywhere. Would that even make a difference?
Did you flash the ics ruu leak..if you did and are going back to gb there's a sd card patch he made. Also amon ra has a version 3.15.
Not sure if anything I said may help....just some ideas/thoughts.
Sent from my ADR6425LVW using XDA
I just realized, you're right ... I'm using Amon 3.14, not 3.15 ... But I don't see the download for 3.15 on the link that Scotty provided ... Anyone know where I can get it from?
Here you go....
http://forum.xda-developers.com/showthread.php?p=23781936
from my ADR6425LVW using XDA
Thanks. Again, I followed Scotty's "temporary recovery" instructions. This time, however, the md5 in the command window did not match the md5 at the link you gave me ... ?
This is probably a big no-no, but I flashed it anyway ... Nothing bad happened to my phone, but it gave me exactly the same message I described earlier.
Still no CWM alternative for nand backups.
Thanks for helping me with this, everyone ... mega thanks.
Guess I'm going to move my questions to another thread, since they're becoming more about nandroid than CWM (or finding an alternative to CWM).
bloodymurderlive said:
Guess I'm going to move my questions to another thread, since they're becoming more about nandroid than CWM (or finding an alternative to CWM).
Click to expand...
Click to collapse
CWM does have some problems but all of them are fixable from what I understand. The alternative to CWM is AmonRa. There really isn't anything else.
i choose the cwm route.... i am now flashing back....cwm will NOT charge a dead battery or let you turn it on.....u have to keep messing with it or boot into bootloader to charge...its a pain in the butt
Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Okay so I recently got this phone more or less as a toy and have been playing with its hardware and software to get it up to par and usable. I've been very impressed by this thing. I ended up with Trackball optional recovery and CM7 Condemned running very well. I seen Gin-sen-tazz and decided to give it a whirl.
Booted into recovery, did a nandroid then wiped data cache and dalvik and then went to flash the rom. It wouldn't go, told me to do something via adb. So I went to restore the backup of cm7 and get a new download ( didnt verify any md5's )
The back up restore gave me the same sort of error, then told me to do something else via adb. I was pretty peved off at this point and went into rom manager and flashed cwr and made a back up of the fresh cm7 install via cwr, and then tried to install the rom via rom manager and then manually in cwr and it still failed.
I'm still downloading my second copy of the rom and I'll be reporting back, but is there any harm in having both recovery's? I really would prefer to run cwr but I have heard of a few bricks, how wide spread is the epidemic? Boot loader still pushes me into trackball optional recovery when selected.
Just kinda sucks that I have two recoveries and neither will work. I am not very new at the whole rom flashing thing but I am not an expert by any means, and have not yet taken the time to learn my adb skills which I know I should
Alright downloaded and put the new rom on the sd card, booted into trackball optional and it flashed just fine.
I also used cwr to back up cm7 and then restore cm7 just to see if that backup indeed worked, and it did. Now I'm concerned that I don't have a stock back up, I made one in trackball recovery but it wont restore... The only back up I have that's working is the cm7 one via cwr... what would you guys recommend i do?
If you decide you want to flash back to stock 2.1 at some point, there's a couple simple options.
Flashback21 will get you back to the latest OTA(March 2011)...unrooted completely stock 2.1.
http://forum.xda-developers.com/showthread.php?t=792026
This other also gives you the latest March 2011 unrooted stock OTA but leaves your custom recovery.
http://forum.xda-developers.com/showthread.php?t=984274
Dunno if this is what was going on, but the Nandroid restore in Amon_RA for the Eris (and derivatives including the trackball-free recovery, I presume) have a 30% battery charge requirement.
If your battery isn't charged above that level, you'll just get a cryptic message about running nandroid-mobile.sh from adb; it won't say "charge your battery, please".
It pays to read Amon_RA's original post, where he points out that you should always check the recovery log file - the exact reason that you could not run the restore operation is reported in that log file. Rather than complaining about an unknown problem on a forum, you would instead know exactly what the problem was.
You can get at the file ( /cache/recovery/log ) via adb while the same recovery session is running, or you can use the Amon_RA menus to copy it to your SD card for later review. It's just a plain text file. Every time you boot the recovery, it gets overwritten - so you need to either review it right away after a problem occurs, or save it to the SD card.
bftb0
OK I am still a bit confused/overwhelmed with how to get my phone to the OTA update. I am unlocked, rooted, stock ROM, and have AmonRa recovery. Just wanted to make sure i have all my ducks in a row before pulling the trigger on this thing.
1. Make a nandroid backup...CHECK...one thing i do know how to do
2. I know I will have to revert back to stock recovery for the OTA to go through.
-I am going to used Clean flash to flash the stock recovery (as it seems to me to be the most noob friendly way)
-Once i have flash stock recovery with clean flash I am good to go recovery wise, i.e. that's all i have to do to replace AmonRa?
-Will replacing AmonRa give me issues with my nandroid since i used AmonRa to make it?
3. Then go into settings and proceed with the OTA
4. After OTA completes flash (with Cleanflash) AmonRa to replace stock recovery
-do I have to delete anything with the stock recovery?
5. Restore nandroid backup to restore root?
Thanks guys in advanced...I am determined to figure this thing out, not only for this but I am still trying to wrap my brain around all the terminology and all the processes not just for this but I really want to branch out and install custom ROMs as well. Might look at making some instructional videos for us noob Rezound users that learn better my seeing something done versus reading how its done. Also if anyone is willing to jump on teamview and help me out that is a option as well.
and again THANKS.
1) Make nandroid
2) Go to the first post in this thread http://forum.xda-developers.com/showthread.php?t=1467329 and download the ROM. Note, all you have to do here, is download and flash.
a) To flash, get into recovery
b)go to option to flash .zip menu
C)if you downloaded this with your phone (you should have) you need to go into the "download" folder
d)click on the ota update zip.
3) IF your wifi and wireless tether are not working after you have flashed! Go to this thread http://forum.xda-developers.com/showthread.php?t=1467793 first post and FOLLOW THE INSTRUCTIONS!
a) the ph98img needs to be on the root of your sd card. The root of your sd card is when you have it plugged into your computer as a disk drive, its the first set of folders that pops up when you open the drive for your sd card. (if that makes any sense)
Voola, you are now on the new ROM, with wifi working.
eta a-d and if you scroll through recovery with volume keys, select with power key. Follow the instructions after the rom flashes.
Mmmmk, everything went fine till I get to step 3.
Did have issue with wifi not working. I tried to do both files but it wanted to instal the PH file first which i canceled. Removed the PH file and just flashed the wifi fix. rebooted, but still no wifi. thought maybe i did something wrong so I tried it again. The my phone stated bootlooping, so now i am restoring the nandroid backup. Any further help would be appreciated.
Okay think I am good to go.
download quickboot from the market.
Boot phone up,
download files,
use quickboot to get you into recovery
flash the 2.6 file FIRST
developer menu back into hboot
let ph98 flash
reboot phone
delete ph98 off of root
If I can piggy back on your thread, I too have some questions re: getting the OTA that I haven't yet found direct answers to.
1.) If using the [ROM] Stock Rooted OTA ROM w/ Firmware to get to the OTA, is the stock recovery still necessary? Or can I do this from Amon Ra? (I'm currently running Tachi's De-Sensed ROM with Amon Ra recovery, and I know my mainver is still 1.xx)
2.) If stock recovery is necessary, is a stock ROM necessary too? For example, is it necessary to have a stock ROM on the phone BEFORE flashing the stock recovery?
3.) It doesn't seem as if relocking is necessary either, is it? Do you have to relock only if you're trying to run the RUU?
thanks all (including OP)
sdsurferbob said:
If I can piggy back on your thread, I too have some questions re: getting the OTA that I haven't yet found direct answers to.
1.) If using the [ROM] Stock Rooted OTA ROM w/ Firmware to get to the OTA, is the stock recovery still necessary? Or can I do this from Amon Ra? (I'm currently running Tachi's De-Sensed ROM with Amon Ra recovery, and I know my mainver is still 1.xx)
2.) If stock recovery is necessary, is a stock ROM necessary too? For example, is it necessary to have a stock ROM on the phone BEFORE flashing the stock recovery?
3.) It doesn't seem as if relocking is necessary either, is it? Do you have to relock only if you're trying to run the RUU?
thanks all (including OP)
Click to expand...
Click to collapse
Someone correct me if I am wrong, PLEASE!
If you lock your phone, and run the ph98 img, your mainver will be updated.
You will have to relock if you want the new radios, I didnt unlock originally and everything worked fine.
I cannot for the life of me coax my Rezound into creating a nandroid backup. I kind of a n00b, so I'll give you my info and how I rooted.
ROOT
I rooted by following Scotty's noob friendly root guide: http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html
I followed his instructions for "temporary recovery" which installed Amon RA 3.14
MY CURRENT SOFTWARE
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
FIRST ATTEMPT
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were.
I selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection.
It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
SECOND ATTEMPT
I installed ROM Manager.
I selected "Flash ClockworkMod Recovery" ... not realizing exactly what I was doing. None the less ...
I booted into CWM.
CWM freezes while making a nandroid backup. Every time. Battery pull. Every time.
THIRD ATTEMPT
I followed Scotty's "temporary recovery" instructions to install Anon RA 3.15 (different version this time)
The md5 in the command window did not match the md5 at download site (http://forum.xda-developers.com/showthread.php?p=23781936)
Seeing no alternatives, I flashed it anyway ... Nothing catastrophic happened.
Did same thing I did in the first attempt, and it gave me the same message.
Anyone have any other ideas?
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
You realize that after the OTA your backup won't work right? If you're just trying to cover yourself between now and then, maybe just copy your whole system and data partitions manually??
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
I don't understad why I can't enjoy these things and create a nandroid backup of my current ROM in case I decide to try other ROMs.
Are you saying that a permanent recovery is the difference between it working and not working?
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
bloodymurderlive said:
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
Click to expand...
Click to collapse
I can't say for certain because I've never gone through that situation before, but if you want to be stock...Why not just let the OTA update you to ICS stock and keep it as it is? Do you really like Gingerbread Stock that much? I guess I just don't understand your reasoning behind all of this. If you were flashing a new ROM after wiping everything in a recovery I would understand your need to nandroid...
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
bloodymurderlive said:
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
Click to expand...
Click to collapse
The firmware that is updated with an OTA update will most likely break Gingerbread compatibility if you try to restore a temporary nandroid backup.
With S-Off none of this would be a problem because we would just flash old radios and kernels right from recovery. HTC makes it difficult to downgrade
uToTMeH8
I want to have the option to return to whatever ROM I want.
If I OTA-update to ICS, I want the option to return to GB (especially given how notoriously buggy OTAs are).
If I install a custom ROM, I want the option to return to stock if I don't like it.
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
bloodymurderlive said:
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
Click to expand...
Click to collapse
This is why everyone is going mental about s-off in this thread:
http://forum.xda-developers.com/showthread.php?t=1578449
Honestly unlocking your bootloader, flashing Amon-Ra and backing up your stock is the way to go. I've had my phone unlocked for 3 months with no problems and the devs on this site are amazing! You're going to want to try every gingerbread ROM once you get really good at backups and flashing. I was getting around 6-8 hours on the stock ROM for battery life. I flashed NilsP's Business Ginger Sense and I hit 30 hours. It's ridiculous how much better battery life is after stripping the ROM down and adding tweaks.
This Toolkit really makes it very easy...Good Luck!
http://forum.xda-developers.com/showthread.php?t=1504824
The error is commonly not enuff space on the SD,or insufficient battery charge.
It has nothing to do with leaving the stock recovery in place.
The only reason you won't be able to restore your gb backup after ics is the fact that it takes a different hboot and.radio,and until the s off method is released,there is no way to revert those. With htcdev,you can only go fwd,not back.
MrSmith317 said:
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Click to expand...
Click to collapse
uToTMeH8 said:
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
Click to expand...
Click to collapse
the reason for leaving the stock recovery is simple: a custom recovery will not install an OTA.
if you leave the stock recovery in place,the OTA will happen,quite naturally,and without isrupting your personal data. sure,it will break root,and anything youve frozen will pop back up,so you do have the minor inconvenience of re-freezing some bloat,and re-launching the temp recovery to flash root files. not a big deal,IMO. remember,htcdev is more like s-off in that you will always be able to root,or re-root. its not an exploit that will disapear.
even if a person wishes to permanently install a recovery,i strongly recomend to get into the habit of launching recovery from fastboot when messing with your phone. as we know,htcdev only unlocks boot,recovery,and system,and we cannot write 'boot' from 'recovery'.
however,launching recovery from fastboot(what ive been calling a 'temporary' recovery) does allow recovery to write to boot. it doesnt do much good(yet) for flashing,as rom devs are still not including the neccessary scripts to install the kernel,but it does allow you to restore nandroids without a seperate kernel flash,making them quicker and easier.
until you switch to ICS firmware(i.e.,install the leaked ruu,or take an OTA) you can flash,backup,and restore any gingerbread roms,and GB firmware based ICS roms,as you desire.
again,what the guys were trying to say when the said you cant restore the GB backups after ICS is simply because the hboot and radio are different. sure,you can physically power up your recovery and restore a GB backup with ICS hboot and radio(firmware),and it will restore,and even boot. you will just have issues due to the incompatible firmware,such as the disapearance of your SD card
hope that helps clear a few things up for you. sorry the above reply was short,i was trying to reply on my phone at work
edit:
one last thing: since youve downlooaded rom manager and used it to flash clockwork recovery,you now have a permanently installed clockwork recovery. you can still temp launch amon with cw in place,but you now are missing the stock recovery,and as such will not be recieving OTAs. if this is important to you,you need to download the stock recovery,and permanently install it(fastboot flash recovery recoveryname.img)
http://www.mediafire.com/?wb21d2gdurui2c6
Thanks Scotty!
First, I'm a complete moron and assumed that my 32GB microSD had enough space. I deleted a movie and made my backup.
One question though about the CWM recovery ... I was concerned that it was permanently installed. However, I attempted to boot into recovery from my phone (power + volume down), and it booted into what looked like the stock recovery ... No dark Amon or CWM recoveries ... Is it possible that CWM didn't permanently flash after all? I know that I have been in both Amon and CWM, and CWM was installed from within the ROM Manager app ...
Are you sure you were in recovery, because power and volume down boots to the bootloader, called boot, which is entirely different.
Sent from my ADR6425LVW using xda premium
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
bloodymurderlive said:
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
Click to expand...
Click to collapse
Yes, Once and OTA is released it should not be long till someone posts here the zip install of the same OTA. Give it another day and I say you will see a cleaned up debloated, rooted etc... zip of the same OTA. These days there is really no need to rush for the OTA downloads, let the Dev's do their magic and offer you something better than Big Red will offer.
Was able to unlock on HTC Dev after doing the jcase exploit and then flashed the CWR 6.0.1.2 with the larger font, unsecured kernel, then got Superuser on it and my phone runs great!
Being somewhat lazy, I like being able to access CWR as the program on the phone, not having to power down and boot into it using Vol Down + Power...so I installed CWR 6.0.1.5 and all seemed fine.
After tweaking all my programs and getting my phone exaclty how I like it I attempted to do a Nandroid backup and about halfway the backup in CWR the phone just stopped and rebboted...no finishing up message, no generating MD5 sum etc that Im used to.
The final backup had 2034 files and was approx 1.2 GB in size.
That didn't seem rigtht so I uninstalled CWR on the phone, then reflashed through fastboot the CWR 6.0.1.2 I originally had....and the phone was then able to do a complete backup....5131 files and about 2.3 GB in size.
I'm pretty sure I was right in not trusting the 6.0.1.5 ROM backup, but any reason why? Is there a version that installs as a program on the phone that will work, or until S-Off is achieved is the proper way into CWR done through powering down and doing the proper reboot to get into recovery?
Sorry for the long winded question...lol but I figure the exact details/methodology will stop any questions back and forth in terms of what I did and why I am asking the question.
From what I've read/heard the version you had was very unstable. Which is why most devs went with TWRP. The fixed version is back up now if you want to give it a shot.