Hi,
I flashed my phone with the HTC 2.3 dev release. Whilst it had some of the new features I wanted, it broke bluetooth to my car which was a deal breaker. I read plenty guides, got revolutionary, s-off'd and installed clockworkmod. That all worked well (seemingly).
I decided to try for the first time a custom rom rather than try and put back the original htc one. I tried leedriod. Used the install from zip method with cwm to install. It installed but just get stuck in a reboot loop. I tried CM7. That installed fine. Whilst the phone is now running with CM7, there are a lot of problems I think related to the boot loader.
If I try to install anything from the sdcard .zip via cwm, it always fails with cannot install zipfile (BAD). Tried hundreds of times! I obviously managed it the first time to get leedroid and cm7 installed.
Cannot establish a connection with the PC to the sdcard when the phone is running and copy anything for more than a few seconds.
usring rom manager, it always says cwm is not installed when it is and trying to re-install hangs near the end.
In cm7, reboot from power button just hangs.
I tried revolutionary again to re-flash cwm. That worked, but no difference. I've a feeling all the above are connected.
I've tried using cwm to do a full wipe, reformat sdcard etc.
Anyone any suggestions? Phone is a bravo with hboot 1.06
First off, rom manager's is pants, don't use it.
Bad zip file is usually a broken download, check the files md5 sum against the original, or just download it again.
Then clear all userdata and try the update.zip again.
Related
I know, first thing to do is search search search... maybe I'm using the wrong keywords but I just cannot find a solution to my problem...
I had rooted with Simple Root OTA and was using DamageControl 3.2.3
Since Froyo came out I decided to unroot and just go stock to test it out
From what I had read, I could just run RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe and all would be fine. I hit the USB connection error and just restarted the exe as stated and all was fine until I hit the Bootloader Version error and then my phone was stuck in a boot loop. My phone now has HBOOT version 0.79.0000 and cannot boot.
I can still get to my custom recovery (RA) so I tried to NAND restore my DC backup and same thing, boot loop. (I also stupidly lost my original NAND backup so cant even try that)
So now I have no idea what to do, I just know there is a solution but for the life of me cannot find it anywhere.
Sigh, please someone, help an Android newcomer...
Since you have Amon Ra wipe the data and cache then install another ROM.
If you want to use Froyo, CM6 or Backed Snacks are both good choices.
A bit more in-depth:
On PC
1. Download the ROM of your choice
On Phone
2. Boot to Amon Ra
3. Put it in storage mode
On PC
4. Move the ROM you downloaded onto the phone.
On Phone
5. Take it out of storage mode
6. Wipe data/cache/dalvik cache
7. Choose "Install from ZIP" then choose your ROM
8. Let it install then boot
9. You should be set
I tried such a step with Fresh 3.0 and unfortunately it was no dice.
I just finally hit upon a solution before I passed out from frustration and exhaustion.
I ran the newest RUU 1.47.* and copied the rom.zip over and renamed it to PC36IMG.zip to install it directly from the phone and it worked like a charm, I then upgraded to Froyo via the OTA.
The speed increase (thanks to JIT) and better battery life is all I really wanted, I can wait until its rooted to get back anything I miss.
Thanks for they reply
ch3vr0n5 said:
I tried such a step with Fresh 3.0 and unfortunately it was no dice.
I just finally hit upon a solution before I passed out from frustration and exhaustion.
I ran the newest RUU 1.47.* and copied the rom.zip over and renamed it to PC36IMG.zip to install it directly from the phone and it worked like a charm, I then upgraded to Froyo via the OTA.
The speed increase (thanks to JIT) and better battery life is all I really wanted, I can wait until its rooted to get back anything I miss.
Thanks for they reply
Click to expand...
Click to collapse
but you do know 2.2 roms are out so you unrooted and went to stock 2.2 instead of downloading an existing 2.2 rooted rom : \
Today I started using CyanogenMod 7 nightly build #27 on my HTC Incredible. Everything was going great and I loved gingerebread. I used it for several hours and decided to make it permanent. I unmounted my sd and formatted it on my PC, after making a copy of all its contents of course. I re-mounted the card and started getting low space warnings, so I figured I should just restart. When I restarted, Cyanogen went into an infinite boot loop. No worries, I had a nandroid backup on my PC from a few hours before Cyanogen. I flashed back to rooted 2.2 Sense stock rom. New issue, I can't access anything on the sd. It appears empty, and none of my widgets can load. So I figured why not just start all over re-root and all of that. I followed a downgrade guide for an out of the box experience,(shouldnt have). The downgrade seemed to be successful but now my phone only boots to the white screen with the skateboarding androids. I have Bootloader, Reboot, Reboot Bootloader, & Power Down. I dont think I have root and I dont have clockwork anymore. Maybe if I could get clockwork back I could get back to 2.2 at least and use rom manager to get back to cyanogen 2.3.
What can I do???
SOLVED
Goto:
http://www.incredibleforum.com/foru...kwork-hangs-htc-incredible-splash-screen.html
Ok, the easiest way to fix this:
1. Format your sd card to FAT32 on your computer
2. DL this recovery zip: http://fourty.net/~berzerker/bamod/PB31IMG-red.zip
3. Place that zip on the root of your sdcard, rename to PB31IMG.zip
4. With the phone off, insert sdcard
5. Hold "Volume Down" and power button until a white screen pops up
6. It should scan for files, and find the zip on the sdcard
7. Press "Volume Up" to confirm update, you should see a progress bar top right.
8. When finished, select "No" when asked to reboot
9. Select "Recovery" with volume keys, confirm with power button.
You should now boot into ClockworkMod recovery. Wipe all data/factory reset, then format your sdcard (optional, just make sure PB31IMG.zip gets erased). You can then mount usb mass storage from "mounts" menu, and copy over CM7.
Stuck at HTC Incredible screen
Hey,
Thanks so much for your quick reply! I was able to flash the recovery you linked me too which has made my day a lot better already, but it seems its not quite over yet.
I wiped all the data, wiped the cache, fomatted the sd, mounted the sd to my pc and copied over CM7.
The first try I also copied over the signed google apps package I received from rom manager, which was in my backup.
Installed them both and the phone never made it past the white HTC Incredible Screen.
So I wiped again and only installed CM7. Same issue.
I have a nandroid backup of 2.2 rooted but otherwise stock HTC Sense rom, but I can't find the recovery on the sd. I copied over my entire old clockwork folder, but its nowhere to be found. I realize the recovery img you gave me looks a lot like clockwork but is titled BAMod Recovery. Could that prevent me from seeing the clockwork folder?
Thanks so much for your help with this!
I'm going to try flashing the radio back to 2.xx
and then try CM6 stable and see what I can get
FU3L said:
I'm going to try flashing the radio back to 2.xx
and then try CM6 stable and see what I can get
Click to expand...
Click to collapse
NO!!!
Flashing a radio is probably not the greatest idea.
Instead, do a search for clockworkmod recovery for the inc. The link I gave you was the one I had on hand, since I wrote all that at midnight lol.
Another thing I'd do is to re-download CM7 from the official teamdouche mirror site, along with g-apps, as I have a feeling your backups are somewhat corrupt.
Ok I won't reflash the radio. But right now the radio is 1.xx
Doesn't CM7 require a 2.xx radio? It rolled back during the stupid downgrade I did.
I've started downloading CM7 and g-apps again. And I will replace BAMod with clockwork. I can do that with the same steps as before right? It will just overwrite BAMod?
FU3L said:
1. Ok I won't reflash the radio. But right now the radio is 1.xx
Doesn't CM7 require a 2.xx radio? It rolled back during the stupid downgrade I did.
2. I've started downloading CM7 and g-apps again. And I will replace BAMod with clockwork. I can do that with the same steps as before right? It will just overwrite BAMod?
Click to expand...
Click to collapse
1. In that case, yes, flash a 2.XX radio.using a PB31IMG. Froyo and gingerbread both require it.
2. Yep, just follow the steps, it'll just overwrite it.
I flashed the radio successfully, something worked!
However I'm having a hard time getting clockwork. I donwloaded clockwork 2.5.0.7 img
I then put it in a zip called PB31IMG
The phone picks up on it and flashes through some things pretty quick the last being parsing PB31IMG.zip....
Then it just jumps back to HBOOT. It doesn't ask if I want to update like the radio did.
I even tried to push it over fastboot from my pc, but everytime it says Failed remote not allowed.
Since I have the correct radio I am trying to flash CM6.1 to see what happens. BAMod is installing it now. If I can get in and get rom manager it can flash clockwork.
Thats my thinking anyway
It says it installed CM6.1 successfully, but still hangs at white HTC Incredible screen on startup
Wiped and installed CM7 successfully but still hung on white HTC Incredible screen.
Should I try using fastboot on my PC to erase the recovery partition? clockwork just gets rejected everytime, the only thing thats seemingly different about the phone now is having BAMod recovery install things instead of clockwork, which worked...
I miss my incredible
Flashed Amon Recovery, installed CM7 build #27. Still hanging on boot screen.
VICTORY!
Here's how I got it working again:
Head over to h**p://dougpiston.com/?page_id=108 site (due to me being an absolute noob to this forum, I can't post links, so just replace h**p with http) , and pick up the PB31IMG version of the original stock HTC image. Flash it, and everything should start up as fresh as the day you bought it. It seems it loses root and custom recovery though, so just reapply and all should be well.
I rooted my DINC a couple of days ago with revoked 3.32. I flashed to Cyangen 6.?? (stable). I didn't like it so i tried to go back to factory settings. I am now stuck.
I made a backup recovery but didn't save an extra one onto my pc. I am now stuck on htc incredible (white screen) boot loop. I am able to get into recovery mode. Did a wipe data/factory reset, wipe cache partition, back up and restore - restore folder, reboot. now stuck in boot loop. Did I do something wrong? Is the recovery file corrupt?
Not too savy on technical words/acronyms.
Try Stock
You can always try to reinstall one of the stock ROM's
http://www.shipped-roms.com/shipped/Incredible/
how do i do that from recovery mode?
Ummm
Those are all .exe files you run on a Windows machine that you have connected your phone to.
well apparently i can't do that cause it won't recognize my connection. Well I played around some more and downloaded Redemption v.2.4. Copied to the root of the sdcard, and ran an update through the recovery. Now running Redemption 2.4.
Thank you for your help!!
At the moment I've got about ten ROMs and at least 2 dozen mods and kernels for those ROMs. Some work really well, some just get funky over time, and others just explode as soon as I flash a mod to them. HeyItsLou ROMs like the one you have are very solid work.
Here's the thing though... you don't have to go in and rename every new ROM you flash to update.zip. you can go to "install .zip from SDcard", then go to whatever folder the ROM is in. It makes it much easier to keep track of your ROMs, kernels, and mods. It works exactly the same, you just have to tell it where to look instead of letting it assume it on the SDcard root.
Also, if you look on the SDcard, you'll find a folder with all of Lou's kernels. His come with number 4, but 8 is probably faster. It's just as easy to flash as a ROM.
Thinking about it, it takes flashing the actual ROM, then flashing 7 additional .zips to get mine where I like it. So you can see where having to rename every update becomes almost impossible. You'll get the hang of it and get more comfy. These things really are hard to brick if you're using ROMs and mods that are decently built. Just nandroid backup (I do it twice if I have none already) and keep a spare ROM on the SD and you'll be totally fine.
Sent from my ADR6300 using XDA App
Hey guys,
So here's what happened and is happening:
1. I was running a custom ROM (Baked Snack 1.7) on Froyo (2.2). The phone was working fine but I wanted to try Gingerbread 2.3.3 out because I heard it had great battery life.
2. My phone would not update to 2.3.3 from Baked Snack. I thought it might have something to do with it being rooted. I used this method to unroot...and I think I only got through the first part:
http://www.thedroiddemos.com/2010/09/10/how-to-unroot-the-evo-in-2-steps/
I installed the S-On tool like he said to. Then I moved the "new updated version" of PC36IMG (I had the old version on my card already). He said something about the "S-Off" appearing on his phone but not the viewer's...well, mine says S-Off.
So fast forwarding, I got Sprint to push me the update for 2.3.3. It downloaded it, but then a voicemail error came up saying I had 2 voicemails. Then when I called voicemail, it said I had no messages. Sprint said a Sprint store would have to physically go into the phone to erase the error.
I also got a second update message that said there were minor enhancements to Gingerbread. I tried downloading them but the installation failed. Sprint told me to ignore the update, that there had been issues with Gingerbread (and the update) and that they were working on getting these resolved.
Somehow I managed to clear the phone and get back to 2.1. Here's what my system says when I look at the Phone Information:
Firmware Version: 2.1-update1
When I boot into the main bootloader/Recovery menu (Phone Off + Power Button + Volume Down), here's what it says:
Supersonic EVT2-2 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
If I click down to Recovery from this menu and press "Power" to enter it, NOW I get a picture of an EVO with a Red Triangle/Exclamation Point. This means I have to take my battery out and restart the phone.
Also, the OTA SimpleRoot procedure doesn't seem to work on the phone either. When I originally set it back, the procedure worked. Now it just goes through the motions on the computer but nothing happens with the phone (rebooting, skating Androids, etc.)
All I want to do is basically put it back 2.2 and re-run Baked Snack 1.7 which was giving me NO issues.
If someone could help me with this issue, I would be very grateful.
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
teh roxxorz said:
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
Click to expand...
Click to collapse
You like TWRP better??
I haven't tried it yet
HipKat said:
You like TWRP better??
I haven't tried it yet
Click to expand...
Click to collapse
Basically amon ra, but better. it has some additional options, such as the option to automatically reboot after a successful flash [good for doing a single flash, but if you're doing multiple, checked it at the last flash.] You have the option to compress backups to save space, though it takes a little bit longer, and they have some built in skins you can change at will. And MOAR.
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
nbakid2000 said:
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
Click to expand...
Click to collapse
That's a bit outdated; use unrevoked. I've already done the linking for you.
1. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- Download and install the modified hboot drivers, follow the instructions.
2. On your phone, enable usb debugging from the applications > development, in settings
3. Connect your phone to your pc via usb cable, leave it on the home screen, no apps should be running; restart the phone just to be sure.
4. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- download and run unrevoked
It'll take 3-5 minutes and reboot about 2 times, don't touch in the process, it'll say done at the end. Also, this will only work if on 2.2 still. if on 2.3.3, you're outta luck.
Okay, forget Rom Manager, forget "rooting" your phone - at least according to the normal use of the word.
Delete any PC36IMG files you may have on your SD card, then download this one of Amon Ra 2.3: http://db.tt/WP0beNa
Don't rename it, don't extract it... just put it on the root of your SD card. Then download whatever rom you want to use. Put it on the root of your SD card or in a folder that you'll remember. Amon Ra (and possibly other recoveries) can flash zips that are inside of folders. Just be sure that you know where it is because you'll need to navigate to it in recovery.
Then boot into the bootloader and let it flash the way you've done with other PC36IMG files. When it asks you to reboot just decline and then select recovery. I would make a backup just in case, then flash your rom.
Sent from my PC36100 using Tapatalk
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
nbakid2000 said:
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
Click to expand...
Click to collapse
Well between plainjane and myself, you'll be rooted before dinner time!
teh roxxorz said:
Well between plainjane and myself, you'll be rooted before dinner time!
Click to expand...
Click to collapse
OK, I forgot to mention this earlier...last time I was stuck in the Boot Sequence where it kept looping the Sprint and 4G logo....now that I'm rooted using plainjane's method (thank you) I'm stuck with the same thing.
I flashed the recovery, then flashed the Baked Snack ROM....now I'm in the Baked Snack bootload section....and it just keeps looping.
Is this an issue with my system that can be resolved?
EDIT: So weird. I went back into Recovery and wiped everything and set the phone back to original condition...and voila, Baked Snack comes up as the ROM! So now it appears it's for the most part back to normal and back to where I wanted it....thank you guys again.
Now can anyone point me in the direction of the latest radios, etc. that I can download and flash?
And why would it be giving me those looping problems, and then go back to normal when I cleared/wiped everything?
I mean, I'm happy this happened but I don't want the same things happening if I decide to flash another ROM at some point.
Hello,
I'm having trouble getting the following ROM to boot after install:
http://forum.xda-developers.com/showthread.php?t=1493404
I have the following:
-S-OFF
-HBOOT-0.76.2000
-RADIO-26.03.02.26_M
-ClockworkMod Recovery v5.0.2.7
I copied the new ROM to SDcard, rebooted to recovery. Performed factory data reset, installed the zip from SD card. It installs successfully, attempts to boot, after white screen with green HTC logo, it reboots to recovery.
I ran an MD5 check on the zip file, verified it was correct. Copied it to SDcard and tried again, no luck. Then I tried installing it from within ClockworkMod Recovery, including wipe options, same thing.
Any ideas?
I'm running into the same issue with most sense 3.5 roms. Beatsrom, Blissdroid, and this one...
But I don't have issues with some others like Andromadus and some MIUI rom that looks like WP7(I can't recall it's name)..
I'm pretty confused on what's wrong since I always do a full wipe before flashing.
If you have a T-Mobile G2, and want to run sense 3.5 roms, you have to install desire z bootloader. I have not done it myself, but here is a video on how to do it. I'm sure if you search there are other guides on how to install the desire z bootloader.
http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html
http://www.youtube.com/watch?v=ogZfSWLlvPg
Perfect. Thank you.
Yup, thanks a lot.
Tip to those trying this at home: once you are done with it, remove the PC10IMG.zip from the root of your SD card to be able to boot into recovery without it asking to reflash. Thanks again ACHILLES R32.