[Q] Newbie struggling to update from 2.2.1 - Wildfire Q&A, Help & Troubleshooting

Hello,
I've only just got this HTC Wildfire but nearly all apps say they are not compatible, so I thought I would try to update, but seem to be hitting problems:
Android version: 2.2.1
HBOOT-1.01.001
Boot menu: HBOOT BUZZ PVT SHIP S-OFF
Initially tried the links to unrevoked but the downloads always seem to time out
Now I tried the [Full Guide] All in one...
I've managed to install the HTCSync drivers OK
I've updated the Android 1.0 driver from the all-in-one package, but when I'm in the boot menu, my Windows XP machine give an error message
- something about a device problem, to try again and if it fails to replace the device. On a different USB port the device driver reports that it failed to start.
Anyway, I ran revolutionary from the all-in-one package but, not surprisingly, it got stuck - it was waiting for fastboot - which is reasonable if the device isn't being recognised.
So, what can anyone suggest?
- If HBOOT already reports S-OFF, can I skip this and still install a newer ROM? If so, how - if I don't have the revolutionary S-OFF?
- Should I give up with Windows and try Linux?
There is a good chance, I suppose , that I have missed something fairly obvious - applogies if that is the case.
I look forward nto any suggestions you may have.
Cheers

dusty_bin said:
Hello,
I've only just got this HTC Wildfire but nearly all apps say they are not compatible, so I thought I would try to update, but seem to be hitting problems:
Android version: 2.2.1
HBOOT-1.01.001
Boot menu: HBOOT BUZZ PVT SHIP S-OFF
Initially tried the links to unrevoked but the downloads always seem to time out
Now I tried the [Full Guide] All in one...
I've managed to install the HTCSync drivers OK
I've updated the Android 1.0 driver from the all-in-one package, but when I'm in the boot menu, my Windows XP machine give an error message
- something about a device problem, to try again and if it fails to replace the device. On a different USB port the device driver reports that it failed to start.
Anyway, I ran revolutionary from the all-in-one package but, not surprisingly, it got stuck - it was waiting for fastboot - which is reasonable if the device isn't being recognised.
So, what can anyone suggest?
- If HBOOT already reports S-OFF, can I skip this and still install a newer ROM? If so, how - if I don't have the revolutionary S-OFF?
- Should I give up with Windows and try Linux?
There is a good chance, I suppose , that I have missed something fairly obvious - applogies if that is the case.
I look forward nto any suggestions you may have.
Cheers
Click to expand...
Click to collapse
Hey pal
take the attached file and rename it to pc49img.zip and put it onto your sdcard. boot the phone into hboot with the sdcard in and the hboot should ask you to update, select yes.
this will add a custom recovery to your device. once this has completed remove the file from your sdcard via computer and then move back to the phone. reboot into hboot and select recovery using the volume rocker and hit power to enter it,
now your ready to go as far as flashing a custom rom is concerned. i would strongly advise making a nandroid backup as this is your main way to restore your phone if issues occur.
the controls for clockworkmod recovery are different from hboot, the can be found in one of my how too threads if you get lost. most of the roms in the dev section have instructions in thier OP for flashing them so just browse around and remember the limitations of this phone, updates wont make it epic but if you use cm7 or higher you should get market apps again.
Good luck and enjoy browsing our corner of the forum

heavy_metal_man said:
Hey pal
[...]
the controls for clockworkmod recovery are different from hboot, the can be found in one of my how too threads if you get lost. most of the roms in the dev section have instructions in thier OP for flashing them so just browse around and remember the limitations of this phone, updates wont make it epic but if you use cm7 or higher you should get market apps again.
Good luck and enjoy browsing our corner of the forum
Click to expand...
Click to collapse
Hi and thanks.
Before I saw your message I had managed to get through the revolutionary issue by using the secon USB port and removing and reinserting the USB plug each time it got stuck. Now I think of it, I has also reinstalled the drivers using the HTCdriver.exe file before that but still had the same issues as before.
Anyway it didn't seem to change anything except that Revolutionary message at the top of the HBOOT screen.
Now I have flashed the image file you possed and I can get into the CWM-based Recovery v5.0.2.8 menu screen. I got stuck at that point but went to you FAQ post to reconfirm that the power button should select the menu item, but it doesn't. Well, it just flips between the menu sceen (with the orange circular arrow behind) and the hat with the circular arrow - but nothing happens.
So I'm back to scratching my head...
Anyway, thanks again - I've managed to get a bit further and would be interested in any further thoughts you may have

dusty_bin said:
Hi and thanks.
Before I saw your message I had managed to get through the revolutionary issue by using the secon USB port and removing and reinserting the USB plug each time it got stuck. Now I think of it, I has also reinstalled the drivers using the HTCdriver.exe file before that but still had the same issues as before.
Anyway it didn't seem to change anything except that Revolutionary message at the top of the HBOOT screen.
Now I have flashed the image file you possed and I can get into the CWM-based Recovery v5.0.2.8 menu screen. I got stuck at that point but went to you FAQ post to reconfirm that the power button should select the menu item, but it doesn't. Well, it just flips between the menu sceen (with the orange circular arrow behind) and the hat with the circular arrow - but nothing happens.
So I'm back to scratching my head...
Anyway, thanks again - I've managed to get a bit further and would be interested in any further thoughts you may have
Click to expand...
Click to collapse
When in clockworkmod recovery you need to press the trackball button to select instead of using power
Sent from my Desire S using Tapatalk

heavy_metal_man said:
When in clockworkmod recovery you need to press the trackball button to select instead of using power
Click to expand...
Click to collapse
Oops - that's rather embarrassing.
I thought I had read power button or trackball and, although I had seen trackball mentioned before, I had never knowingly used it and certainly hadn't realised where it was or that there was a button function associated with it
Next, I'll check out your nandroid backup app recommendation, although I don't really have much on this phone yet. I did a backup from CWM already.
In the set of files I have downloaded while reading various threads , I have cm-7.2.0-buzz.zip and cm-7-20130301-NIGHTLY-buzz.zip. I suppose either of these should be fine, or do you have some other recommendation?
Thanks - I appreciate your patience...

dusty_bin said:
Next, I'll check out your nandroid backup app recommendation, although I don't really have much on this phone yet. I did a backup from CWM already.
In the set of files I have downloaded while reading various threads , I have cm-7.2.0-buzz.zip and cm-7-20130301-NIGHTLY-buzz.zip. I suppose either of these should be fine, or do you have some other recommendation?
Thanks - I appreciate your patience...
Click to expand...
Click to collapse
Its all good pal the back up you made from recovery Is a nandroid back up (from a fusion of the words nand and android I believe. Nand being the memory type used in older android phones) I would recommend any cm7 7.2.x roms as they are very stable usually. Remember that you will also need flash gapps (Google apps) for cm7 which can normally be found in the roms description.
Sent from my Desire S using Tapatalk

heavy_metal_man said:
Its all good pal the back up you made from recovery Is a nandroid back up (from a fusion of the words nand and android I believe. Nand being the memory type used in older android phones) I would recommend any cm7 7.2.x roms as they are very stable usually. Remember that you will also need flash gapps (Google apps) for cm7 which can normally be found in the roms description.
Click to expand...
Click to collapse
Cheers -I installed the cm 7.2.0 file and gapps - and everything went fine this time :victory:
It looks like the next challenges wil be to avoid running out of memory - the phone memory is already down to 20 MB even though I've moved all the apps I can to the SD card. Working out where everything is in new settings menu can be quite interesting too
One final question: if I want to install the later version of cm7 (or an even higher version), can I just use 'upgrade from SD card' from the CWM menu item, to avoid having to reinstall everything?
Thanks again!

Yes and no. if your upgrading to a later version of cm7, IE 7.2.3 or 7.3 you could flash it over your rom with minimal issues but if your changing android version dramatically like from gingerbread to Ice cream sandwich or jelly bean then a full wipe is recommended along with nandroid backup before flashing or wiping anything

Related

[Q] Rooting random issues?

I'm pretty new to this rooting for Android, I recently got my Incredible.. I used unrevoked to root my incredible. I did it normally like USB debugging and all that. Soon as it started to root it, the phone rebooted itself like it was supposed too, got to the HTC Incredible screen (the first screen on the boot up) and black screen and white bars on the sides. Now I got this phone like November 27th.. and I'm pretty postive my screen is an SLCD? And that seems to be what the problem is with the black screen white bars.. Thing is, of course the black screen white bars stayed there, so I pulled the battery out and put it pack in. It loaded up normally and it seemed to be rooted fine. It had the Superuser (ninja). And everything was normal. I downloaded ROM Manager and then downloaded the Flash ClockWorkMod Recovery, and then I clicked on Cynagen Mod and went down to Google apps. Downloaded it, installed it, then it asked to reboot. ALL OF WHAT I JUST DID, (followed from The Start to Finish Guide to Rooting Your Android Phone, I con't post links yet) .. So as it rebooted it got the HTC Incredible screen (the first screen on the boot up) and it did the black screen white bars. I removed the battery either twice or three times.. And still nothing, I THEN FOLLWED THIS Incredibleforum dot com (I rooted and now I only see a black screen with white bars in recovery.) and went to the Hboot menu and went down to recovery and selected it. It rebooted and still black screen white bars at the HTC Incredible screen. I then tried his other method and went to download that file and went to unrevoked and did the custom recovery and put recovery in the file and plugged my phone in. ( He actually said to like check USB debugging, which I couldnt actually do because I couldnt get to my menu..) So then after plugging it in and showing the orange light for charging. It did nothing other then charge. I turned it on ( I'm pretty sure, it might have turned on by itself) and it worked. It got the menu screen. And everything was the same. ROM Manager was still there, same with superuser. And the 3 game apps that I downloaded before I rebooted for Google Apps. I haven't found Google Apps, I'm not really sure where Google Apps would be anyways.. But what I'm getting at here is, What actually happened????? Why those white bars?? And will this happen everytime I have to reboot? If someone could just give me their best answer or an explanation It would really help. I'm new to this stuff.. But I'm getting nervous with this black screen thing white bars.. and I'm debating wether to just unroot..(how easy is unrooting?).. But my phone is fine now, I haven't tried like downloading anything but everything seems to be working fine.. Where could I find Google Apps? And which ROM? Cynagen Mod Or Bugless Beast.. Please Help
You have an slcd screen. Your recovery is for smiled. Use unrevocks recovery for slcd screens. As I have read you need that one for recovery to work properly. I don't have an slcd so I don't know to much about that end
Just cruise the forums there is tons of info out there.
Sent from CM Nightly 11-20 using Tapatalk.
I had similar issues, and poster above is correct... I was able to flash a modified clockwork recovery to get it working with slcd...but I'm halfway afraid to try any ROM Manager abilities due to the different recovery :>
Just flash the modified Clockwork- very simple and works perfectly. I have the zip if you want it.
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
mcolib8 said:
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
Click to expand...
Click to collapse
http://www.megaupload.com/?d=7O9ZPP2T
You don't need to uninstall anything from your phone obviously, but I'd uninstall any unrEVOKed stuff from your computer before you do the new version. Recovery is basically the tool that lets you modify the phone. You go there to do nandroid backups and restores, and to flash zips. Let me know if you need instructions on how to apply the fix.
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
mcolib8 said:
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
Click to expand...
Click to collapse
1. Mount your phone as disk drive (I'm assuming you know how to do that, if not, lemme know)
2. Move the file to the root of your sd card (not in any folders) and make sure you don't re-name it at all.
3. Disconnect your phone, wait for the card to format, and then yank your battery.
4. Put the battery back in, hold Volume Down+Power.
5. You'll see your bootloader and it will find the file automatically, let it install it.
6. Once it's done, yank your battery again and repeat Step 4.
7. This time, choose not to install it, and instead choose Recovery- should load up Clockwork just fine. Easiest way to access Clockwork in the future is thru ROM Manager- there's an option to boot into recovery.
PS. might wanna check your clockwork version first thru ROM Manager- my version is 2.5.0.5 and I'm not sure if Koush has included the SLCD fix in any of the newer versions, so I'd make sure you have that version before doing this.
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Edit... responded too late. Thanks for the advice!
Sent from my ADR6300 using XDA App
ithuwakaga said:
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm guessing you didn't read to the end of the thread before you posted
iBowToAndroid said:
I'm guessing you didn't read to the end of the thread before you posted
Click to expand...
Click to collapse
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
ithuwakaga said:
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
iBowToAndroid said:
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
Click to expand...
Click to collapse
Thank you!
Sent from my ADR6300 using XDA App

[Q] clockwork problems

I've just got my first Android phone (an HTC Desire from Telstra - quite a good phone from all reports but hobbled almost to the point of unusability by Telstra). My Android guru (also a member of this forum) has had little success rooting it so it can be made more useful because, although most of the process works, it seems that Clockwork is not going in successfully and doesn't seem to be able to recognise the SD card (8GB, partitoned at 7GB (FAT32) and 1 GB (EXT3)). It claims that it can't find several of the files it needs to work.
The upshot is that, although the screen comes up with the options of things to do (restore etc.), when selected it just hangs with a black screen.
I checked some other similar threads but couldn't come up with anything.
Please pardon any inanity - I'm very new to this.
Any help most gratefully accepted. Thanks
when selected it just hangs with a black screen.
Click to expand...
Click to collapse
When selecting the option use the centre trackpad to select not the power button...
However i'm also new to a Desire (i have a desire hd) and have exactly the same on the Desire i rooted with Unrevoked last night, for example if i try to wipe system or data it just comes up with an error message...
Any ideas thanks...
Just tried to run unrevoked again to see if recovery would install properly this time.
Yesterday it said it was a triumph this time it says failed to get root is the software to new...
Is that because its already rooted or it didn't actually work properly yesterday ?
Thanks
After reading a bit on google and on this forum seems that Unrevoked may be the issue someone else with the same problem got it sorted by using Unrevoked 3.21 rather than the 3.32 that the unrevoked website installs...
Next question anyone know where i can get 3.21 been googling and can't find anything that will actually download..
Again many thanks
wakers said:
After reading a bit on google and on this forum seems that Unrevoked may be the issue someone else with the same problem got it sorted by using Unrevoked 3.21 rather than the 3.32 that the unrevoked website installs...
Next question anyone know where i can get 3.21 been googling and can't find anything that will actually download..
Again many thanks
Click to expand...
Click to collapse
How about PMing the person who sorted the problem out to see if they still have 3.2.1 on their machine? I thought I did but on checking I've got 3.3.2 - sorry!
Hi
I had to use AlphaRev to be able to flash custom firmware. Unrevoked did root the phone but didn't s-off. If you plan to use Unrevoked VirtualBox method get VBox v3.xx, v4.xx has something messed with usb passthrough
Sent from my HTC Desire using Tapatalk
I managed to find a version of the unrevoked that was suggested but it hasn't made any difference...
I've been ages reading and going around in circles
The Hboot is 0.93.0001
The phone appears to be rooted as superuser is on it and appears to be working.
THe phone will boot into recovery but recovery doesn't work
I've tried using a different recovery with rom manager but it makes no difference when i boot into recovery its the same Clockworkmod recovery 2.5.0.7 even though in Rom manager it says its changed...
As it boots into recovery there are a few messages underneath
e:cant find misc:
e:cant mount cache : recovery/command
and a few other lines which i can't remember but similiar
I've tried removing and flashing a different recovery via adb and i get a message saying "remote not allowed"
I've tried flashing recovery with a terminal emulator but can't get it to work either.
Do i need to do the alpharev to get S-Off first before i can sort out recovery ? and if so any info on how to do this, again many thanks and sorry for so many questions.
I've rooted Magic's, Legends, HD2's and my Desire HD but this desire for my missus does have me a bit stumped...
I wonder if fake flash would help in this situation?
Might be a viable way to get recovery functioning...
http://forum.xda-developers.com/showthread.php?t=698403
As it boots into recovery there are a few messages underneath
e:cant find misc:
e:cant mount cache : recovery/command
and a few other lines which i can't remember but similiar
These look like about the same as the ones I get
OK... I don't know why, but this worked for me (and my guru). Instead of pressing the power button as the enter button during the rooting and restore process, we pressed the mouse button and it all worked fine. The errors still showed up but they didn't cause any problems. I think this might have been one of the first suggestions but I seem to have missed it (this is what you get when you stay up 'til stupid-o'clock trying to sort stuff out).
I'm up & running now and I hope this helps some others having the same issues.
Thanks to all those who provided suggestions.
gen_scheisskopf said:
Hi
I had to use AlphaRev to be able to flash custom firmware. Unrevoked did root the phone but didn't s-off. If you plan to use Unrevoked VirtualBox method get VBox v3.xx, v4.xx has something messed with usb passthrough
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Just to clarify this point, Rooting and S-OFF are 2 totally different things.
Root access is to the loaded ROM on the phone. It allows you to gain access to places you normally can't go inside android like \system and \recovery
S-OFF is turning signature verification off in the Bootloader. the bootloader is the lowest system level you can go and as such can do some pretty serious things there.
jimmytheflea said:
Just to clarify this point, Rooting and S-OFF are 2 totally different things.
Click to expand...
Click to collapse
Yes, I know this. S-Off option was selected in Unrevoked menu (and didn't work). AlphaRev 1.8 (LiveCD) didn't work on unrooted phone but after rooting did it's job
Finally success i think sometimes you can read so much info you get confused.
Did alpharev via CD and installed alpharev-cwm recovery option and its all working as it should be, can't believe how simple it turned out to be in the end...
Thanks to all who replied much appreciated...
Hello, i am using oxygen 2.0.3 ROM now. I had been flashing roms with recovery for a few times. But now, it seems like recovery is unable to detect changes to my sdcard.
Whenever i boot into recovery to install zip from sdcard, it will show me the folders and zip files that i had before. Any changes i made to the sdcard was not reflected.
I search through the web and this forum and you seems to have the closest issue that i am experiencing. It would be great if you can advice if your method can solve my problem as well and what are the detail steps you took to solve it. Thanks alot man.
Hi mate the issue i had was that recovery didn't seem to install properly at all and i could see the rom etc on the sdcard and any changes i made but it wouldn't work, i also had issue's with not being able to push commands through adb.
What worked for me was creating the Alpharev ISO image on a CD and running it following the instructions, it was incredibly simple but i had a stock rooted rom on my desire.
The alpharev instructions are here
http://alpharev.nl/
Downloadf the Flash utility then burn the flash utility (still zipped) to a CD shut down your laptop press F12 as it boots choose boot from CD once the laptop screen goes black plug your phone in (i had mine on charge only) you also need to make sure USB debugging is checked...
And follow the instructions for me it S-Off'd the phone and installed the Alpharev-CWM recovery which is working as it should...
Not sure thats going to cure your issue though as it seems you have an issue with your recovery reading the SDcard this wasn't an issue for me...
cheongster said:
Hello, i am using oxygen 2.0.3 ROM now. I had been flashing roms with recovery for a few times. But now, it seems like recovery is unable to detect changes to my sdcard.
Whenever i boot into recovery to install zip from sdcard, it will show me the folders and zip files that i had before. Any changes i made to the sdcard was not reflected.
I search through the web and this forum and you seems to have the closest issue that i am experiencing. It would be great if you can advice if your method can solve my problem as well and what are the detail steps you took to solve it. Thanks alot man.
Click to expand...
Click to collapse
Do you see changes made to sd card when booted rather than in recovery i.e. if you add a zip to SD and reboot to your rom, do you see the SD, then you don't see it if you reboot again to recovery?
stringer7 said:
Do you see changes made to sd card when booted rather than in recovery i.e. if you add a zip to SD and reboot to your rom, do you see the SD, then you don't see it if you reboot again to recovery?
Click to expand...
Click to collapse
Yes. I see the changes made to the SD card in my ROM. But the changes don't get reflected when i am in recovery.
Is your issue occurring after you mount the card in usb mode in recovery and then adding file and then trying to flash that zip? if so, then you can see that file by choosing reboot recovery option
Swyped with my Starburst Classic based Desire with Intelligent Data2sd
I transfer the files while i turn on the usb for data transfer in the rom. Do i have to do the file transfer while i'm in recovery?
I used to be able to do it previously. I am not sure what happened along the way and it stopped working now. I did delete all the files on my SD card before having this issue. Not sure if thats the course and if there is a fix for that.
Thanks!
Well if you were doing it while booted up, sorry I have no idea why it doesn't work then.
Solution is to reflash your recovery
Swyped with my Starburst Classic based Desire with Intelligent Data2sd

Revolutionary on new wildfire problem (or extreme muppetry)

Hello everyone.
I enjoyed the noob video and also look forward to being pasted no doubt.
I have a wildfire running 2.2 android which I understand means I am running the latest firmware, which I also understand is going to make it difficult for me to root easily.
Never the less not being one to be beaten I have tried with EVO3, which no matter what I tried would not work, constantly asking if my firmware was too new. I even wiped it but no luck.
So I struck upon revolutionary, which yes I understand is beta.
This is perhaps where my lack of understanding comes in. Would I be right in thinking that custom roms require a specificly rooted device?
The thing is I have apparently been successfull with revolutionary. I can boot into it and I was able to instaly cryongena rom which worked OK until I installed google apps where by it constantaly showed the spinning blue arrow, round and round, rebooting and rebooting.
Thing is all other roms I have tried, everyone, has failed, with either script being old 'error 6' etc etc.
I found I needed a different kind of rom, which a few were offering however these also failed with error 6 which apparent was something to do with not being pure unix or something.
Sorry I am not up on the language, but I think I have tried all the popular ones, puzzle etc and none will install.
When I start up with the volume button pressed it shows the screen then says something about failing to load image, but goes away to quick to read pc4diag.img or something.
Is it possible I have not loaded revolutionary correctly, and have I gained 'root'
Thanks for reading, and please feel free to tear me a new one.
- Yes, I am sure you have Revolutionary installed correctly. You got a bootloop while installing GApps, in which case I would recommend performing a full wipe in Clockworkmod and try to install again. (Install the CM ROM first, then the GAPps Zip. Also, I hope you are using a filename called gapps-gb-2011xxxx.zip)
- If you want to install other ROMs, Sense and Android 2.2.1 ROMs require Clockworkmod 2.x. Attempting to flash them in Clockworkmod 3.x/4.x will give you the "Scripting not supported" error. The workaround to this is to download this attachment:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
Flash this in your new Clockworkmod Version, which will give you temporary 2.5, then proceed as normal.
- When you boot into the HBoot Mode, it will automatically perform a search for the files PC49IMG.diag and .nbh. It's normal, and theres nothing to worry about. After the search is over, and, it has not found the files, you can navigate properly again.
Oh, and I think you are being too paranoid about the video and everyone here trying to tear you a new one.
Good Luck
Thanks very much for your answer.
Honestly I spent 2 hours on google last night trying to get my head around it.
To be honest all I want is a quick phone, and I am not getting that with stock software on my wildfire, I get very frustrated when trying to scroll but it reads it as me tapping an app icon, and there are loads of them I don't want in here, footsteps and tweets and the likes, I am simply not interested and neither am I allowed to remove them. The cynogenmod looked amazing, but I can see even more processor intensive than the stock software.
I will have a look at what you have suggested and thanks for your help!
In that case, I think you might want to stick with the Stock ROM, and, get an app like 'Root Uninstaller' or 'Titanium Backup' which allows you to uninstall (Or, to be more correct - 'freeze') any apps you wish - Including System Apps.
Not trying to advertise Cyanogenmod here, since I understand ROM preference is a personal thing, but, I would recommend giving it one more try, after a full wipe. Also, go with the latest nightlies rather than the Stables. I have been using it since it was released back in January, and, honestly, I am never going back to Stock / Sense based ROMs.
Don't get me wrong it looks awesome. But the boot up time was just shy of 4 minutes (although I now understand it may have been because of first boot) and two attempts at install failed.
I shall look at how to fully wipe, but to be honest, being very new to hacking my phone I am quite happy having the back up there to revert too.
Well I tried to install anything but nothing works so I shall revert to my original back up and see about these tools for removing unwanted apps.
Thanks for the help, but something is not right. All roms either get as far as the twinkly noise on the HTC screen then do it again and again, and cynogen gets to the rotating arrow, then eventually an android zips across the screen and back to the arrow
Well I don't think I have root on this device. I tried to install busybox and titanium and both tell me my phone is not rooted.
Sigh.
If you are on the Stock ROM, you will have to flash this additionally:
http://bit.ly/su2361ef
This will install Superuser, which is what will give you "root". If you are on Custom ROMs, flashing this additional file is not required, since, they include the Superuser Binary already,. So, flash that, and then try installing Busybox / Ti Backup. (make sure you get a "superuser" icon in your app drawer after flashing that zip)
EDIT:
- Are you on Clockworkmod 3.0.0.6 incidentally? That version has caused bootloops for many users when installing ROM's.
- First boot time is extremely long (Upto 7-8 mins), and its normal.
Hello thanks for the info.
I am not confident I know what mod I am on, I just went to the revolutionary website and downloaded the latest beta.
When you say it can take 7-8mins to load up would this include the boot loops though? Thats all I get on all of them
I shall install the super user bit see if that helps.
No, not including bootloops. BTW, I am referring to the Clockworkmod Version, not Revolutionary,
When you enter the Recovery to flash something, at the bottom, you will "Clockworkmod Version x.x.x.x". It is that version I was asking.
Sadly I am not getting anywhere here, every single rom just goes round in circles in one way or another.
The version say revolutionary CWM v4.0.1.4
I was unable to get the standard revoked installed as I am runnning the latest android firmware and it just kept failing.
Something I am getting rather used to!
I cannot see a clockwork mod number anywhere, although it must be there as I have clockwork folder on the SD card.
Sorry, I am being a muppet here.

Boot Loops, forever.

So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!
Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App
i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...
Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App
I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.
You can also try wiping /system and /boot.
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)
wow... what a bummer. thanks for the help anyway, it's much appreciated.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium
I'll try it again to verify the code, I'm pretty sure it was "170"
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had
sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468
This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App
=D
Sent from sweet snacks off tapatalk.

Confirm Steps & Apps to Install New ROM on G2 (Mimicry 1.3.2)

I have had my G2 for about 18 months and have been running into a lot of issues recently. I've decided to fix those issues by rooting & getting a new ROM installed. I'm a tech savvy guy, but have not done anything on the phone end due to not wanting to break whats working. I've decided to go with the Mimicry 1.3.2 ROM since the install process uses Aroma and is very straight forward. Before I pull the trigger, I just want to make sure I have all the steps clear so that I don't go "Oh sh**" in the middle because I missed a step. There's also a couple of steps that I'm not clear on. Here's what I researched:
-Root phone using HTC's bootloader unlocker
-Format phone's flash memory to EXT4
--What is the best app to do this with? Will my phone work with Gingerbread after I make this change?
-Download Mimicry 1.3.2 and Google Apps put the zip files on my phone (not SD card)
-Power off phone and then push the volume down and power buttons together and choose to install the ROM
-Answer prompts in Aroma (including installing WiFi calling)
-Flash Google apps
--How exactly is that done?
-Restart phone and start setting up apps again.
Does that look correct and is there anything that I'm missing? Thank you in advance for your help.
Well first off I would stay away from HTC official unlocked bootloader, its worthless and will give you headaches in the future
use the wiki to root, either follow the wiki in cyanogen or here on xda, if you even slightly tech savvy it will be easy
following that guide you will have clockwork recovery, but I suggest moving to 4ext recovery, among many reasons is the ability to format to ext4. Otherwise the next easiest way to format would be to flash a super wipe script with ext4 format written to it (just search xda and you'll find it easier)
Now after you are rooted with an engineering s-off hboot consider flash the .19 radio, not super important but many find this to have the best reception and battery life.
Next make sure your SD card is fat32, I also suggest an ext4 partition there as well (easily done through recovery) but skip the swap
Now feel free to flash mimicry, and may I add this is one other best ICS Roms for the vision, and blk_jck is a very helpful Dev as well.
Good luck, if you run into issues there will be answers all over xda, just search a bit, happy flashing!
Sent from my Nexus 7 using xda premium
Thanks
Thanks for the heads up on the HTC bootloader. I'll check out the Wiki on how to PermRoot my phone.
Mimicry, recovery, soft bricks, and new ROM
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
1.3.2 adds few framework level changes and no device level changes. Definitely nothing that should cause errors or problems booting anyway.
Sent from my HTC Vision using xda premium
Good Info
timram said:
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
Click to expand...
Click to collapse
Thanks for that info. I am taking a look at the Cyanogen Wiki and seeing what I have to do. I'm thinking that I will jump directly to Mimicry 1.3.2 instead of installing Cyanogen 9 first. Hopefully that file doesn't hang out there and causes that boot loop to happen to me (thanks for that explanation, BTW).
So do I have to use that ClockworkMod to load the ROM, or does EXT4 do the same thing (as far as loading the rom goes)?
...where thanks is due
many thx, blk jack, I should have specifically mentioned your awesome contributions as well, and
have remedied with thanks meter as i came/come across it.
Will re-try the 1.3.2 shortly. If I run in to the same glitches, I will try and make note of the specific errors
(or any other bugs, for that matter) and let you know.
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting
Checking it out now
iamnoobie said:
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
Click to expand...
Click to collapse
I'm actually looking at that wiki right now. I just finished backing up all the contents on my SD card. I can't backup the apps on my phone since it's not rooted, and I can't use a backup app unless I'm root. So it looks like that is a catch 22. Personally, I don't mind wiping everything anyways since I'm going to be making the jump to ICS. I guess I'll have to beat all those levels in cut the rope again :crying:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
timram said:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
Click to expand...
Click to collapse
Thanks for that. I've now downloaded the Android SDK and am now trying to test the connection to my G2 using adb. So far, no connection. Grrrr. I'm looking around now to see how to get my phone detected by adb since it doesn't seem to have anything on the cyanogen wiki.
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
HTC Sync
demkantor said:
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I tried the adb devices command and it didn't return any connected devices. Looking in the xda wiki, they are saying that I need to have HTC Sync installed. I'm downloading that right now. They probably should put that in the cyanogenmod wiki also.
I got my phone detected by adb! I did some preliminary checking and I think I should be good to go on rooting. I think I will root my phone tomorrow when I have plenty of time to troubleshoot any issues that my come up.
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
prairie-dad said:
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Click to expand...
Click to collapse
Cyan wiki worked for me! (strawmetal didn't - I blame myself though).
ext4 and mimicry are what I'm running now (after going through CWM, CM 7.2 and CM9 RC1 & RC2) and I'm very happy with both. Mimicry is great!
prairie-dad said:
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
minor glitches, but rooted and s-off fine
demkantor said:
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
all went well till the very, very, very end. I went to reboot into clockwork recovery, and...nothing doing! holding down the trackball, volume down and power...and waiting and waiting...just got me into the bootloader with no option to go to recovery...just reboot, reboot the boot loader, and power down.
So I thought, maybe I somehow failed to get the recovery img where I wanted it...no big deal. I logged onto the old Market (this is 2.2, after all) and purchased 4ext (which is what seems to be everyone's choice) and installed it. Then I said I wanted to reboot with mimicry and gapps, hit "go," and...it rebooted into ClockworkMod Recovery...where it now sits, I assume backing up the existing system. Mimicry 1.3.2 and gapps images were sitting on my sdcard root, btw.
Very odd, and a little perplexing...I will wait it out a while before powering off and up again.
any thoughts? Must I remove clockwork mod manually (I assume that when I installed 4ext it made itselfthe default recovery method...) or does 4ext just sit atop Clockwork Mod...and what I am seeing now is normal...? I've been waiting a few minutes now, and see nothing but the Clockword Mod icon, the top hat.
Sigh...but pretty clearly almost all the way home.
Thanks to all,
dave
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
darn ClockWorkMod/4ext clash!
demkantor said:
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
---------- Post added at 07:33 AM ---------- Previous post was at 06:42 AM ----------
prairie-dad said:
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
Click to expand...
Click to collapse
Mimicry is booting now. All good. I ended up using the clockwork mod version, 3. something, that I installed when following (too slavishly?) the CM wiki's instructions (otherwise excellent!) Then (and now) I have problems booting into the bootloader, and it doesn't show a recovery option... Running 4ext (which I purchased) seems to be great (looks really useful) until rebooting...when CWM comes up instead.
I kept using volume up or down to pick what I wanted, then pushed the power button to select...wrong! It's the trackball you click, which I only hit upon by accident. Once I got that working, I flashed mimicry and Gapps, and I am off to the races again.
Thanks to all, but I want to figure out what is with recovery for the future.
What buttons do I push to get to bootloader...so far all I have gotten to work is via USB cable and "dab reboot boot loader."
dave

Categories

Resources