[Q] clockwork problems - Desire Q&A, Help & Troubleshooting

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

Related

[Resolved] Boot Loop Issue -- please help if you can!

I'll give my question first, then the history. I tried to search the EVO 4G subforums and couldn't seem to find it. If there's a post on this please kindly point me in the right direction.
Regardless of which ROM I install on my EVO except for what I understand is the engineering ROM or possibly the stock ROM, I go into a boot loop.
History:
- Did not install any updates or use unrevoked after receiving my EVO
- Did the root method known as "part 1" before NAND unlocking was available, never did any system updates. It seemed I had root because I was able to use the sudo "allow" or "deny" and use Wifi Tether in AP mode successfully (the open source APK)
- Was having some random reboot issues so I decided I needed to finally get an updated, custom ROM on my phone
- Yesterday spent many hours trying to get SimpleRoot to root my phone. However, ROM Manager keeps complaining it can't do privileged commands
- I was able to get Clockwork Recovery onto my phone finally using Unrevoked 3 just to get it on there (with what I know as the engineering ROM)
- Used clockwork to try and install Fresh 1.0.1, DamageControl v3.1.2 or seemingly anything other than that same engineering ROM (that has the HTC logo and sound) puts it into a boot loop. Also Clockwork (the APK) complains it still can't run privileged commands on that ROM from SimpleRoot.
I've been flashing a Kaiser/Tilt since forever but still pretty newb on Android but trying to learn fast. Love my EVO!
If there is any more information I can provide to help someone help me please let me know and hopefully this can help others not go astray as I have...
EDIT: Oh, yes and I read some of the troubleshooting information for different ROMs and one said to reformat sd-ext but my SD card is just formatted how it comes from the factory. I would really like to keep it that way unless it is a must for installing custom ROMs on the EVO. Clockwork did not seem to be able to do the partitioning for me.
EDIT: Now resolved after following thoroughly the directions listed here:
http://forum.xda-developers.com/showthread.php?t=721055
Thanks for helping me out!
aikeru said:
I'll give my question first, then the history. I tried to search the EVO 4G subforums and couldn't seem to find it. If there's a post on this please kindly point me in the right direction.
Regardless of which ROM I install on my EVO except for what I understand is the engineering ROM or possibly the stock ROM, I go into a boot loop.
History:
- Did not install any updates or use unrevoked after receiving my EVO
- Did the root method known as "part 1" before NAND unlocking was available, never did any system updates. It seemed I had root because I was able to use the sudo "allow" or "deny" and use Wifi Tether in AP mode successfully (the open source APK)
- Was having some random reboot issues so I decided I needed to finally get an updated, custom ROM on my phone
- Yesterday spent many hours trying to get SimpleRoot to root my phone. However, ROM Manager keeps complaining it can't do privileged commands
- I was able to get Clockwork Recovery onto my phone finally using Unrevoked 3 just to get it on there (with what I know as the engineering ROM)
- Used clockwork to try and install Fresh 1.0.1, DamageControl v3.1.2 or seemingly anything other than that same engineering ROM (that has the HTC logo and sound) puts it into a boot loop. Also Clockwork (the APK) complains it still can't run privileged commands on that ROM from SimpleRoot.
I've been flashing a Kaiser/Tilt since forever but still pretty newb on Android but trying to learn fast. Love my EVO!
If there is any more information I can provide to help someone help me please let me know and hopefully this can help others not go astray as I have...
EDIT: Oh, yes and I read some of the troubleshooting information for different ROMs and one said to reformat sd-ext but my SD card is just formatted how it comes from the factory. I would really like to keep it that way unless it is a must for installing custom ROMs on the EVO. Clockwork did not seem to be able to do the partitioning for me.
Click to expand...
Click to collapse
i had a similar issue, and so did a few people. i wrote out a post some time ago, i don't know if you read it...
http://forum.xda-developers.com/showpost.php?p=7204861&postcount=4
try that out. let me know how it goes.
EDIT: it also sounds like you don't have nand unlocked.
Thank you for your quick reply! I will try it and report back what I did, what works/didn't.
As a side note...
Since I have Clockwork on the recovery (I can boot to recovery all day long just using volume up and clockwork is there) doesn't that mean NAND is unlocked? Anyway, thank you again.
aikeru said:
Thank you for your quick reply! I will try it and report back what I did, what works/didn't.
As a side note...
Since I have Clockwork on the recovery (I can boot to recovery all day long just using volume up and clockwork is there) doesn't that mean NAND is unlocked? Anyway, thank you again.
Click to expand...
Click to collapse
having a boot recovery program doesn't necessarily mean you have nand unlocked. the ability to flash custom roms does though. good luck! i know it's frustrating, but keep at it.
silly question but are you wiping correctly ?
I had to ask...
elegantai said:
silly question but are you wiping correctly ?
I had to ask...
Click to expand...
Click to collapse
i almost spilled my drink LOL
elegantai said:
silly question but are you wiping correctly ?
I had to ask...
Click to expand...
Click to collapse
lol XD nice ... any comeback I can think of just goes way too far
Well, I've downloaded the files so sometime this evening/tonight I should have results. That post links to what appears to be a very, very thorough set of instructions
http://forum.xda-developers.com/showthread.php?t=721055
So I'll go through the whole thing there and of course report back
aikeru said:
lol XD nice ... any comeback I can think of just goes way too far
Well, I've downloaded the files so sometime this evening/tonight I should have results. That post links to what appears to be a very, very thorough set of instructions
http://forum.xda-developers.com/showthread.php?t=721055
So I'll go through the whole thing there and of course report back
Click to expand...
Click to collapse
lol good luck buddy. it's a relatively easy walkthrough if you follow it closely. post up any questions you have.

[Q] problem flashing myns rls4

help with flashing myns 2.2
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night on my phone and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm
are you s-off, what recovery?
Could be a corrupt download so I would try to redownload the rom and then reinstall. But what hardware version and hboot do you have?
Yes s is on..and the recovery is clockwork..
Wrong section bud, don't post questions in here especially since you already posted in Q&A. But you need your S-OFF thats why your having problems.
definitely need s-off, but have you tried to DL it again?
yea i thought it might be on the wrong forum so i reposted it there after, i apologize. how do i get the s off. Im not very good at this.. im interested in alt his stuff but not very good yet..i thought when i rooted it would turn s off..and yea ive tried installing it several time with no luck and same error
in another thread someone told me that its not working bc im still s-on..how do i turn that off.. hardware version 0003
First, you need to verify whether s is on or off. To do this, power down your phone, and hold the volume down button while you power it back on. It will boot into a white screen with 3 Androids on skateboards at the bottom. The very first line at the top of the screen will indicate if s is off or on.
If you rooted with Unrevoked, s should be off. However, I believe that before you can flash custom roms, you need to unlock NAND by flashing the engineering SPL onto your phone. On the same screen where you see if s is on or off, it needs to say Hboot: 0.76.2000 on the second line. If it has any other version of the hboot, you will not be able to flash custom roms.
This is what I did 1 week ago when I rooted my girl's Evo (also a 0003):
1) Ran Unrevoked for root.
2) Installed ROM Manager to flash recoveries & TI for back-ups.
3) Put Myn's RLS 4 on root of SD, and tried to flash via recovery; got errors similar to yours.
4) Downloaded engineering spl and placed on root of SD
5) Went back into recovery and flashed the eng. spl (at this point, I tried to boot it and the phone had no rom and would loop at the white HTC EVO 4G screen).
6) Got the phone back in recovery by doing a battery pull, powering on while holding volume down, and selected recovery.
7) From the recovery, I flashed Myn's RLS 4, my favorite kernel, a custom boot screen, and then rebooted.
8) Opened a beer and relaxed.
Don't forget to wipe everything twice! Also, before you flash the eng. spl, make sure you go into ROM manager and use the option to "flash an alternate recovery" so you do everything with Amon recovery which does a better job wiping. However, with Amon you cannot navigate through all the folders on your SD card to find what you want to flash. All flashable files MUST be placed in a .zip format in the root of your SD card (meaning out in the open and NOT inside any folders)
I hate using ADB, and if you follow these steps precisely, you will not need it.
Good luck!
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
firmbiz94 said:
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Check your hboot version, and see what it is. If it is hboot 2.02, that is your problem. Unrevoked doesn't work (yet)with that hboot version. Currently, the only way to root that hboot version is the "boss" method. Can be found in the development section. You can check by doing the same thing the guy before mentioned, hold vol down, and power button together. Then you will see the version, at the bottom I think. When did you get your Evo? What hardware version are you? ( settings, about phone, hardware info) software info the same way, see if your build 3.29 or 3.30.
Edit: looks like the thread is now "like a pinecone" rather than "like a boss"
OP: Rooting does not turn s off. Root allows you to run programs that require root access. With root, you can run wireless tether, ROM Manager, Titanium back up, Shootme app for screen shots, etc.
However, to flash custom roms, you need to have NAND access and that is done by flashing the engineering hboot. You can find the engineering hboot here:
http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
Like k2buckley, if you have the 2.02 hboot, you need to follow this root guide:
http://forum.xda-developers.com/showthread.php?t=829045
It requires lots of ADB and this is for more advanced users. If you are going to try it, make sure your battery is completely charged before you start messing with it. I HIGHLY recommend you search YouTube for video tutorias on the root method you need to use and watch it from beginning to end (twice if you need to) to make sure this is something you feel you can do before you dive in.
Merged 2 threads.
I finaLly figured it out..I got frustrated and figured I'd flash unrevoked forever..I downloaded to SD card and flashed it..that turned nand off..then I flashed myns..and it worked..i couldn't believe it..thanks for your help guys..
I downloaded shootme to take a shot of my software to so you guys. But when I try to attach a file it doesn't do anything when I press search..anyways so far I really like the Rom and netarchy kernel..I think I'm gonna be addicted and flash often although I nandroid backed this one since I like it..any other suggestions for sense roms..I just want to have a blazing fast Evo..not sure if I wanna go aosp though..

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.

[Q]I'm kinda confused on a bootloop problem

Hi guys,
I just got into flashing my phone a few weeks ago when my stock desire started giving me endless low memory notifications, so I was attracted by A2SD. Anyways I've read and read, then read some more and I've been able to answer all my own problems up to now.
I rooted, S-offed etc. I installed Pyramid with sense 3.0 as my first ROM but it felt laggy and frustrating to use. So after reading I decided to try CM7. It's super fast and stable but I was finding I just could not figure out how to install apps. It has no market app so I'd go to the market website and install then I just couldn't find the app anywere. Plus it would tell me I had apps installed I didn't, but did on the first rom. I just wiped everything when I installed CM7. I guess I was used to the user friendly sense but I was finding CM7 not as simple.
So as fast and stable as it is I wanted to play with some other ROMs so tonight I got MIUI. It installed nice but as soon as it loaded after about 5 seconds it would reboot. and again and again. I read about boot loops in the thread but couldn't find a definitive answer. I read the boot loop help thread and then tried formatting boot, system, cache, sd=ext and whatever else the instructions said. Wiped again, installed MIUI and same thing.
It's getting late and I need my phone for tomorrow so I thought I'd try Insertcoin. The problem doesn't seem to be just MIUI though because that ROM did the same bootloop. About 5 seconds after everything seems to load properly. Now I'm a little worried.
Tried the last known good ROM, CM7, and viola! Everything is good and stable again. I'm wondering about partition table I didn't flash a new HBOOT. Mostly because I'm not sure how to? I'm unsure about this step (from the alpharev site)
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded).
The part after the arrow is were I'm not sure.
The thing is MIUI says it will go on a stock HBOOT so I figured my bases were covered?
Sorry about the long thread and honestly I've read and I'm ready to ask the community for advice. I've solved several problems on my own and here I am! Hopefully got this in the right fora. Also hope I got all the relevant info in. Any advice or idea on why those two ROMs boot looped would be awesome I still want to try MIUI.
Cheers
Can you give more info, like how you partitioned your sd card. What info does the bootloader in the top left of the screen give you. Wright it all down here. Maybe then its easyer to help.
Sent from my HTC Desire using XDA App
Your phone setup NEEDS TO MATCH developer requirements for that rom... so read instruction and set your phone up
I can't help you with your boot problems,
but I can however help you understanding the
third point in the alpharev description, as I was
facing the same understanding problem 2 days ago.
The command 'fastboot flash hboot bravo_alphaspl.img' is used
via your cmd / konsole/ terminal on your pc.
So what you must do is,
- install android sdk
- connect your desire via usb, go into fastboot-mode
- navigate via cmd / konsole / terminal to the 'platform-tools' folder (there is
the fastboot script you need to trigger) within your android sdk folder
(- you can test if your device is found with the command "fastboot devices")
and..yeah. Enter the commands from the alpharev page in your terminal.
/*Just remembered, you need to install the desire usb drivers, when you
are using windows, or something like that. I'm not using windows, but I'm
sure it's easy to google if you need help on either the usb drivers OR
on how to install the android sdk under windows.*/
MarcelHofs said:
Can you give more info, like how you partitioned your sd card. What info does the bootloader in the top left of the screen give you. Wright it all down here. Maybe then its easyer to help.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I used Gparted to partition the stock 8GB micro SD card that came with my Desire. I have a fat 32 partition followed by a 1000mb EXT4 partition. Bootloader info is:
-----AlphaRev-----
BRAVO PVT4 SHIP S-OFF
HBOOT- 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.027
Aug 10 2010, 17:52:18
Hope this helps if you have any idea what the problem is. The only thing I haven't played with is the radio.
Malso thanks very much for the info I was really unsure how to proceed there! I'll flash the CM7 HBOOT. Cheers.
kotag82 Thats the problem I can't figure out why Pyramid and CM7 work and MIUI or Insertcoin don't I can't figure out where the difference is between CM7 and MIUI that would prevent one from working. I thought my phone was matched exactly for MIUI. an't figure out what changed that one would work and the other just reboots 5 seconds after loading. The flashing of both MIUI and Insertcoin seemed to go perfectly.
Wondering if a full SD format would help? I've read and re-read the MIUI thread it it really looks like I should be good to go?
Yeah never did get my MIUI working. Allways with the rebooting problem. Did get RunnyMede AIO going and I'm loving that. Except for the battery drain issue. It will be fine untill about 50% and then I'll use about a percent every few minutes even with the phone off and in my pocket!

[Q] Newbie struggling to update from 2.2.1

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

Categories

Resources